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

From Andres Freund
Subject Re: Issue in recent pg_stat_statements?
Date
Msg-id 20210426180831.rs3j5pxyudh5twtu@alap3.anarazel.de
Whole thread Raw
In response to Re: Issue in recent pg_stat_statements?  (David Christensen <david.christensen@crunchydata.com>)
Responses Re: Issue in recent pg_stat_statements?  (David Christensen <david.christensen@crunchydata.com>)
List pgsql-hackers
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



pgsql-hackers by date:

Previous
From: David Christensen
Date:
Subject: Re: Issue in recent pg_stat_statements?
Next
From: Andres Freund
Date:
Subject: Re: compute_query_id and pg_stat_statements