Re: Issue in recent pg_stat_statements? - Mailing list pgsql-hackers

From David Christensen
Subject Re: Issue in recent pg_stat_statements?
Date
Msg-id lzy2asvaze.fsf@veeddrois.attlocal.net
Whole thread Raw
In response to Re: Issue in recent pg_stat_statements?  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Andres Freund writes:

> On 2021-04-26 12:53:30 -0500, David Christensen wrote:
>> On Mon, Apr 26, 2021 at 12:18 PM Julien Rouhaud <rjuju123@gmail.com> wrote:
>> > Using pg_stat_statements with a different query_id semantics without
>> > having to fork pg_stat_statements.
>> >
>> 
>> I can see that argument for allowing alternatives, but the current default
>> of nothing seems to be particularly non-useful, so some sensible default
>> value would seem to be in order, or I can predict a whole mess of future
>> user complaints.
>
> +1

Just doing some routine followup here; it looks like cafde58b33 fixes
this issue.

Thanks!

David



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Preventing abort() and exit() calls in libpq
Next
From: Tom Lane
Date:
Subject: Re: Add '--ignore-errors' into pg_regress