| From: | David Christensen <david(dot)christensen(at)crunchydata(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Julien Rouhaud <rjuju123(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Issue in recent pg_stat_statements? |
| Date: | 2021-06-29 17:25:57 |
| Message-ID: | lzy2asvaze.fsf@veeddrois.attlocal.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-06-29 17:59:38 | Re: Add '--ignore-errors' into pg_regress |
| Previous Message | Tom Lane | 2021-06-29 17:15:30 | Re: Preventing abort() and exit() calls in libpq |