Re: Ignore 2PC transaction GIDs in query jumbling

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Julien Rouhaud <rjuju123(at)gmail(dot)com>
Cc: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Ignore 2PC transaction GIDs in query jumbling
Date: 2023-08-01 02:00:32
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Tue, Aug 01, 2023 at 09:28:08AM +0800, Julien Rouhaud wrote:
> Having an application relying on 2pc leads to pg_stat_statements being
> virtually unusable on the whole instance, so +1 for the patch.

Cool, thanks for the feedback!

> 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. 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

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Laurenz Albe 2023-08-01 02:07:24 Re: [PATCH] Add support function for containment operators
Previous Message Peter Smith 2023-08-01 01:35:35 Simplify some logical replication worker type checking