| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Rafia Sabih <rafia(dot)sabih(at)enterprisedb(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Passing query string to workers |
| Date: | 2017-01-11 23:36:26 |
| Message-ID: | 29230.1484177786@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Wed, Jan 11, 2017 at 7:37 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> As far as reproducing the pg_stat_activity query goes, you could probably
>> grab that string out of the master backend's pgstat entry and pass it over
>> at parallel query start. But please don't confuse it with either
>> debug_query_string or the string referenced by the QueryDesc; I do not
>> think there's any guarantee that those are the same.
> I think we should pass only the string referenced by the QueryDesc to
> the worker, and on the worker side report that via debug_query_string
> and pg_stat_activity and attach it to the QueryDesc itself. Is that
> also your view?
That would work, if you had a way to get at the active QueryDesc ...
but we don't pass that down to executor nodes.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gilles Darold | 2017-01-11 23:40:09 | Re: Packages: Again |
| Previous Message | Robert Haas | 2017-01-11 23:13:08 | Re: Passing query string to workers |