Horton
Menu

Re: pg_stat_statements: calls under-estimation propagation

Peter Geoghegan <pg@heroku.com>

View thread
From: Peter Geoghegan <pg@heroku.com>
To: Daniel Farina <daniel@fdr.io>
Cc: Sameer Thakur <samthakur74@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2013-10-02T00:23:01Z
Lists: pgsql-hackers 
On Sun, Sep 29, 2013 at 10:58 PM, Daniel Farina <daniel@fdr.io> wrote:
> I remember hacking that out for testing sake.
>
> I can only justify it as a foot-gun to prevent someone from being
> stuck restarting the database to get a reasonable number in there.
> Let's CC Peter; maybe he can remember some thoughts about that.

On reflection I think it was entirely to do with the testing of the
patch.  I don't think that the minimum value of pg_stat_statements has
any real significance.

-- 
Peter Geoghegan

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Improve management of "sticky" entries in contrib/pg_stat_statements.