| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org> |
| Cc: | Julien Rouhaud <rjuju123(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Ignore 2PC transaction GIDs in query jumbling |
| Date: | 2023-08-27 08:32:25 |
| Message-ID: | ZOsKGdMHzcvN6cqQ@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Aug 19, 2023 at 01:47:48PM +0900, Michael Paquier wrote:
> On Fri, Aug 18, 2023 at 11:31:03AM +0100, Dagfinn Ilmari Mannsåker wrote:
>> I don't have a particularly strong opinion on whether we should
>> distinguish DEALLOCATE ALL from DEALLOCATE <stmt> (call it +0.5), but
>
> The difference looks important to me, especially for monitoring.
After thinking a few days about it, I'd rather still make the
difference between both, so applied this way.
> And pgbouncer may also use both of them, actually? (Somebody, please
> correct me here if necessary.)
I cannot see any signs of that in pgbouncer, btw.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2023-08-27 11:23:11 | Re: Make all Perl warnings fatal |
| Previous Message | Pavel Stehule | 2023-08-27 04:40:55 | Re: [PATCH] Add XMLText function (SQL/XML X038) |