On Wed, Jan 11, 2017 at 6:36 PM, Tom Lane <t...@sss.pgh.pa.us> wrote:
> Robert Haas <robertmh...@gmail.com> writes:
>> On Wed, Jan 11, 2017 at 7:37 AM, Tom Lane <t...@sss.pgh.pa.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.
Hmm, that is a bit of a problem. Do you have a suggestion?
The Enterprise PostgreSQL Company
Sent via pgsql-hackers mailing list (email@example.com)
To make changes to your subscription: