| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Yun Li <liyunjuanyong(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view? |
| Date: | 2019-03-18 18:33:42 |
| Message-ID: | CAOBaU_bK8fjOzq2VZ8qEGRWh9wE2g5pUH8bFL_n5S+0F0AqyUQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 18, 2019 at 6:23 PM Yun Li <liyunjuanyong(at)gmail(dot)com> wrote:
>
> Let's take one step back. Since queryId is stored in core as Julien pointed out, can we just add that global to the pg_stat_get_activity and ultimately exposed in pg_stat_activity view? Then no matter whether PGSS is on or off, or however the customer extensions are updating that filed, we expose that field in that view then enable user to leverage that id to join with pgss or their extension. Will this sounds a good idea?
I'd greatly welcome expose queryid exposure in pg_stat_activity, and
also in log_line_prefix. I'm afraid that it's too late for pg12
inclusion, but I'll be happy to provide a patch for that for pg13.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-03-18 19:08:19 | Re: jsonpath |
| Previous Message | Nikolay Samokhvalov | 2019-03-18 18:24:19 | Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view? |