Re: Ignore 2PC transaction GIDs in query jumbling - Mailing list pgsql-hackers

From Julien Rouhaud
Subject Re: Ignore 2PC transaction GIDs in query jumbling
Date
Msg-id 20230801022209.4ac2c4shvmu2fnnq@jrouhaud
Whole thread Raw
In response to Re: Ignore 2PC transaction GIDs in query jumbling  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Ignore 2PC transaction GIDs in query jumbling
List pgsql-hackers
On Tue, Aug 01, 2023 at 11:00:32AM +0900, Michael Paquier wrote:
> On Tue, Aug 01, 2023 at 09:28:08AM +0800, Julien Rouhaud wrote:
>
> > FTR we had to entirely ignore all those statements in powa years ago to try to
> > make the tool usable in such case for some users who where using 2pc, it would
> > be nice to be able to track them back for pg16+.
>
> That would be nice for your users.

Indeed, although I will need to make that part a runtime variable based on the
server version rather than a hardcoded string since the extension framework
doesn't provide a way to do that cleanly across major pg versions.

> Are there more query patterns you'd
> be interested in grouping in the backend?  I had a few folks aiming
> for CallStmt and SetStmt, but both a a bit tricky without a custom
> routine.

Looking at the rest of the ignored patterns, the only remaining one would be
DEALLOCATE, which AFAICS doesn't have a query_jumble_ignore tag for now.



pgsql-hackers by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: [PATCH] Add support function for containment operators
Next
From: Amit Kapila
Date:
Subject: Re: Inaccurate comments in ReorderBufferCheckMemoryLimit()