{"push_id":1069942100,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"4039c736eb0955cb1daf88e211f105dbbb78f7ea","before":"5fdda1ceab35311367ed0dbb283cd8aea896e49b","commits":[{"sha":"4039c736eb0955cb1daf88e211f105dbbb78f7ea","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Adjust spin.c's spinlock emulation so that 0 is not a valid spinlock value.\n\nWe've had repeated troubles over the years with failures to initialize\nspinlocks correctly; see 6b93fcd14 for a recent example.  Most of the time,\non most platforms, such oversights can escape notice because all-zeroes is\nthe expected initial content of an slock_t variable.  The only platform\nwe have where the initialized state of an slock_t isn't zeroes is HPPA,\nand that's practically gone in the wild.  To make it easier to catch such\nerrors without needing one of those, adjust the --disable-spinlocks code\nso that zero is not a valid value for an slock_t for it.\n\nIn passing, remove a bunch of unnecessary #include's from spin.c;\ncommit daa7527afc227443 removed all the intermodule coupling that\nmade them necessary.","distinct":true,"url":"https://api.github.com/repos/postgres/postgres/commits/4039c736eb0955cb1daf88e211f105dbbb78f7ea"}]}