Re: query_id, pg_stat_activity, extended query protocol

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Alexander Lakhin <exclusion(at)gmail(dot)com>
Cc: Sami Imseih <samimseih(at)gmail(dot)com>, jian he <jian(dot)universality(at)gmail(dot)com>, Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com>, Andrei Lepikhov <lepihov(at)gmail(dot)com>, kaido vaikla <kaido(dot)vaikla(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: query_id, pg_stat_activity, extended query protocol
Date: 2024-10-04 03:41:01
Message-ID: Zv9jzTgcIBWVam_g@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 03, 2024 at 10:00:00PM +0300, Alexander Lakhin wrote:
> I've managed to falsify the Assert in ExecutorRun() with the following:
> SET compute_query_id = 'off';
> SET track_activities = 'off';
>
> CALL p2(0);
>
> CALL p2(1);

Fun. This manipulates the session to force the state of the first two
conditions, while the PERFORM done at PL-level resets the query ID
and while there is a query string from the top-level CALL. I'll go
revert the assertion for now.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2024-10-04 03:55:45 Re: Rename PageData to XLogPageData
Previous Message Andrei Lepikhov 2024-10-04 03:31:22 Re: POC, WIP: OR-clause support for indexes