Re: query_id, pg_stat_activity, extended query protocol - Mailing list pgsql-hackers

From Andrei Lepikhov
Subject Re: query_id, pg_stat_activity, extended query protocol
Date
Msg-id e3345264-8818-4b9c-aebf-43f1fa492bbb@gmail.com
Whole thread Raw
In response to Re: query_id, pg_stat_activity, extended query protocol  ("Imseih (AWS), Sami" <simseih@amazon.com>)
List pgsql-hackers
On 14/8/2024 23:05, Imseih (AWS), Sami wrote:
>> I think the testing discussion should be moved to a different thread.
>> What do you think?
> See v4.
> 
> 0001 deals with reporting queryId in exec_execute_message and 
> exec_bind_message.
> 0002 deals with reporting queryId after a cache invalidation.
> 
> There are no tests as this requires more discussion in a separate thread(?)
At first, these patches look good.
But I have a feeling of some mess here:
queryId should be initialised at the top-level query. At the same time, 
the RevalidateCachedQuery routine can change this value in the case of 
the query tree re-validation.
You can say that this routine can't be called from a non-top-level query 
right now, except SPI. Yes, but what about extensions or future usage?

-- 
regards, Andrei Lepikhov




pgsql-hackers by date:

Previous
From: Andreas Karlsson
Date:
Subject: Re: JIT: Remove some unnecessary instructions.
Next
From: Tom Lane
Date:
Subject: Re: thread-safety: strerror_r()