Re: Storing pg_stat_statements query texts externally, pg_stat_statements in core - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Storing pg_stat_statements query texts externally, pg_stat_statements in core
Date
Msg-id 21713.1390855179@sss.pgh.pa.us
Whole thread Raw
In response to Re: Storing pg_stat_statements query texts externally, pg_stat_statements in core  (Peter Geoghegan <pg@heroku.com>)
Responses Re: Storing pg_stat_statements query texts externally, pg_stat_statements in core  (Peter Geoghegan <pg@heroku.com>)
List pgsql-hackers
Peter Geoghegan <pg@heroku.com> writes:
> On Sun, Jan 26, 2014 at 10:38 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Meh.  This line of argument seems to reduce to "we don't need to worry
>> about performance of this code path because it won't be reached often".

> I think I may have over-elaborated, giving you the false impression
> that this was something I felt strongly about. I'm glad that the
> overhead has been shown to be quite low, and I think that lexing
> without the lock held will be fine.

OK.  Committed after a couple of small further revisions.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: ALTER TABLE lock strength reduction patch is unsafe
Next
From: Dimitri Fontaine
Date:
Subject: Re: extension_control_path