Tom Lane b2c4071299 Redesign query-snapshot timing so that volatile functions in READ COMMITTED ... mode see a fresh snapshot for each command in the function, rather than using the latest interactive command's snapshot. Also, suppress fresh snapshots as well as CommandCounterIncrement inside STABLE and IMMUTABLE functions, instead using the snapshot taken for the most closely nested regular query. (This behavior is only sane for read-only functions, so the patch also enforces that such functions contain only SELECT commands.) As per my proposal of 6-Sep-2004; I note that I floated essentially the same proposal on 19-Jun-2002, but that discussion tailed off without any action. Since 8.0 seems like the right place to be taking possibly nontrivial backwards compatibility hits, let's get it done now.		2004-09-13 20:10:13 +00:00
..
common	Pgindent run for 8.0.	2004-08-29 05:07:03 +00:00
gist	Pgindent run for 8.0.	2004-08-29 05:07:03 +00:00
hash	Pgindent run for 8.0.	2004-08-29 05:07:03 +00:00
heap	Renumber SnapshotNow and the other special snapshot codes so that	2004-09-11 18:28:34 +00:00
index	Update copyright to 2004.	2004-08-29 04:13:13 +00:00
nbtree	Pgindent run for 8.0.	2004-08-29 05:07:03 +00:00
rtree	Pgindent run for 8.0.	2004-08-29 05:07:03 +00:00
transam	Redesign query-snapshot timing so that volatile functions in READ COMMITTED	2004-09-13 20:10:13 +00:00
Makefile	$Header: -> $PostgreSQL Changes ...	2003-11-29 19:52:15 +00:00