Tom Lane d1cbd26ded Repair two places where SIGTERM exit could leave shared memory state ... corrupted. (Neither is very important if SIGTERM is used to shut down the whole database cluster together, but there's a problem if someone tries to SIGTERM individual backends.) To do this, introduce new infrastructure macros PG_ENSURE_ERROR_CLEANUP/PG_END_ENSURE_ERROR_CLEANUP that take care of transiently pushing an on_shmem_exit cleanup hook. Also use this method for createdb cleanup --- that wasn't a shared-memory-corruption problem, but SIGTERM abort of createdb could leave orphaned files lying around. Backpatch as far as 8.2. The shmem corruption cases don't exist in 8.1, and the createdb usage doesn't seem important enough to risk backpatching further.		2008-04-16 23:59:40 +00:00
..
common	Simplify and standardize conversions between TEXT datums and ordinary C	2008-03-25 22:42:46 +00:00
gin	Push index operator lossiness determination down to GIST/GIN opclass	2008-04-14 17:05:34 +00:00
gist	Push index operator lossiness determination down to GIST/GIN opclass	2008-04-14 17:05:34 +00:00
hash	Phase 2 of project to make index operator lossiness be determined at runtime	2008-04-13 19:18:14 +00:00
heap	Create new routines systable_beginscan_ordered, systable_getnext_ordered,	2008-04-12 23:14:21 +00:00
index	Phase 2 of project to make index operator lossiness be determined at runtime	2008-04-13 19:18:14 +00:00
nbtree	Repair two places where SIGTERM exit could leave shared memory state	2008-04-16 23:59:40 +00:00
transam	Repair two places where SIGTERM exit could leave shared memory state	2008-04-16 23:59:40 +00:00
Makefile	Refactor backend makefiles to remove lots of duplicate code	2008-02-19 10:30:09 +00:00