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.
contrib/pg_stat_statements/pg_stat_statements.c | 57 +++++++++++++++++------
1 files changed, 42 insertions(+), 15 deletions(-)
pgsql-committers by date
|Next:||From: Robert Haas||Date: 2012-04-09 03:06:38|
|Subject: pgsql: Teach SLRU code to avoid replacing I/O-busy pages.|
|Previous:||From: Heikki Linnakangas||Date: 2012-04-08 16:44:38|
|Subject: pgsql: set_stack_base() no longer needs to be called in PostgresMain.|