On Mon, Mar 18, 2019 at 6:23 PM Yun Li <liyunjuany...@gmail.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.
