Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?
От | Bruce Momjian |
---|---|
Тема | Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view? |
Дата | |
Msg-id | 20201014144050.GB9415@momjian.us обсуждение исходный текст |
Ответ на | Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view? (Julien Rouhaud <rjuju123@gmail.com>) |
Ответы |
Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view?
|
Список | pgsql-hackers |
On Wed, Oct 14, 2020 at 10:34:31PM +0800, Julien Rouhaud wrote: > On Wed, Oct 14, 2020 at 10:31 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: > > > > Bruce Momjian <bruce@momjian.us> writes: > > > Is there a measureable overhead when this is turned on, since it is off > > > by default and maybe should default to on. > > > > I don't believe that "default to on" can even be in the discussion. > > There is no in-core feature that would use this by default. > > If the 2nd patch is applied there would be pg_stat_activity.queryid > column, but I doubt that's a strong enough argument. There is that, and log_line_prefix, which I can imaging being useful. My point is that if the queryid is visible, there should be a reason it defaults to show empty. -- Bruce Momjian <bruce@momjian.us> https://momjian.us EnterpriseDB https://enterprisedb.com The usefulness of a cup is in its emptiness, Bruce Lee
В списке pgsql-hackers по дате отправления: