Re: review - pg_stat_statements - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: review - pg_stat_statements
Date
Msg-id CAM3SWZTwrRDtw879m2YB3qFETmBS9UJ=maScKXzm-ayFzopEvQ@mail.gmail.com
Whole thread Raw
In response to Re: review - pg_stat_statements  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: review - pg_stat_statements
List pgsql-hackers
On Sat, Nov 30, 2013 at 11:30 PM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
> After this fix it should be ready for commit

Version with trivial, single token fix attached. I'm not sure if you
just forgot to mark this "ready for committer" in the commitfest app,
but if not you'll want to do so now.

I defer to the judgement of a committer here -- my hope is that the
queryid-exposing patch will be committed soon, and so it becomes a
simple matter of "rebasing" (a term I use loosely) what I've done here
on top of the then master branch. I felt that I had an up-front
responsibility to not regress the aggressive-snapshot-aggregating use
case, which is why I haven't simply waited for the queryid patch to be
committed so that I could only then submit a new patch (a *separate*
patch that allows query texts to not be returned when unneeded).

Thanks
--
Peter Geoghegan

Attachment

pgsql-hackers by date:

Previous
From: Dean Rasheed
Date:
Subject: Re: Re: [BUGS] BUG #7873: pg_restore --clean tries to drop tables that don't exist
Next
From: Andres Freund
Date:
Subject: Re: Incomplete freezing when truncating a relation during vacuum