Kevin Grittner 848ef42bb8 Add the "snapshot too old" feature ... This feature is controlled by a new old_snapshot_threshold GUC. A value of -1 disables the feature, and that is the default. The value of 0 is just intended for testing. Above that it is the number of minutes a snapshot can reach before pruning and vacuum are allowed to remove dead tuples which the snapshot would otherwise protect. The xmin associated with a transaction ID does still protect dead tuples. A connection which is using an "old" snapshot does not get an error unless it accesses a page modified recently enough that it might not be able to produce accurate results. This is similar to the Oracle feature, and we use the same SQLSTATE and error message for compatibility.		2016-04-08 14:36:30 -05:00
..
expected	Bloom index contrib module	2016-04-01 16:42:24 +03:00
sql	Bloom index contrib module	2016-04-01 16:42:24 +03:00
t	Bloom index contrib module	2016-04-01 16:42:24 +03:00
.gitignore	Bloom index contrib module	2016-04-01 16:42:24 +03:00
blcost.c	Bloom index contrib module	2016-04-01 16:42:24 +03:00
blinsert.c	Modify BufferGetPage() to prepare for "snapshot too old" feature	2016-04-08 14:30:10 -05:00
bloom--1.0.sql	Bloom index contrib module	2016-04-01 16:42:24 +03:00
bloom.control	Bloom index contrib module	2016-04-01 16:42:24 +03:00
bloom.h	Fix contrib/bloom to not fail under CLOBBER_CACHE_ALWAYS.	2016-04-03 15:16:07 -04:00
blscan.c	Add the "snapshot too old" feature	2016-04-08 14:36:30 -05:00
blutils.c	Modify BufferGetPage() to prepare for "snapshot too old" feature	2016-04-08 14:30:10 -05:00
blvacuum.c	Modify BufferGetPage() to prepare for "snapshot too old" feature	2016-04-08 14:30:10 -05:00
blvalidate.c	Bloom index contrib module	2016-04-01 16:42:24 +03:00
Makefile	Bloom index contrib module	2016-04-01 16:42:24 +03:00