Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Jim Finnerty <jfinnert(at)amazon(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?
Date: 2019-06-28 18:46:14
Message-ID: CAH2-Wz=hVRsx4hsvBEGJQdMXZHFVRJcmc3c=Snw-KRS+bM8+TQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 19, 2019 at 12:00 PM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On the other hand, it also appears that a lot of people would be very,
> very happy to just be able to see the query ID field that already
> exists, both in pg_stat_statements in pg_stat_activity, and we
> shouldn't throw up unnecessary impediments in the way of making that
> happen, at least IMHO.

+1.

pg_stat_statements will already lose all the statistics that it
aggregated in the event of a hard crash. The trade-off that the query
jumbling logic makes is not a bad one, all things considered.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2019-06-28 18:47:33 Re: Superfluous libpq-be.h include in GSSAPI code
Previous Message Tom Lane 2019-06-28 18:42:49 Re: [HACKERS] Regression tests vs existing users in an installation