Tom Lane d5375491f8 Improve management of "sticky" entries in contrib/pg_stat_statements. ... This patch addresses a deficiency in the previous pg_stat_statements patch. We want to give sticky entries an initial "usage" factor high enough that they probably will stick around until their query is completed. However, if the query never completes (eg it gets an error during execution), the entry shouldn't persist indefinitely. Manage this by starting out with a usage setting equal to the (approximate) median usage value within the whole hashtable, but decaying the value much more aggressively than we do for normal entries. Peter Geoghegan		2012-04-08 15:49:47 -04:00
..
Makefile	Make EXPLAIN (BUFFERS) track blocks dirtied, as well as those written.	2012-02-22 20:33:05 -05:00
pg_stat_statements--1.0--1.1.sql	Expose track_iotiming information via pg_stat_statements.	2012-03-27 15:18:49 -04:00
pg_stat_statements--1.0.sql	Throw a useful error message if an extension script file is fed to psql.	2011-10-12 15:45:03 -04:00
pg_stat_statements--1.1.sql	Expose track_iotiming information via pg_stat_statements.	2012-03-27 15:18:49 -04:00
pg_stat_statements--unpackaged--1.0.sql	Throw a useful error message if an extension script file is fed to psql.	2011-10-12 15:45:03 -04:00
pg_stat_statements.c	Improve management of "sticky" entries in contrib/pg_stat_statements.	2012-04-08 15:49:47 -04:00
pg_stat_statements.control	Make EXPLAIN (BUFFERS) track blocks dirtied, as well as those written.	2012-02-22 20:33:05 -05:00