Re: query_id, pg_stat_activity, extended query protocol

From: Sami Imseih <samimseih(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: jian he <jian(dot)universality(at)gmail(dot)com>, Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com>, "Imseih (AWS), Sami" <simseih(at)amazon(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-09-18 20:13:10
Message-ID: BDBBF18A-7664-4D1C-BDB4-7145C4B5CE5E@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> So, I have applied 0001 down to 14, followed by 0002 on HEAD.

Thank you!

> 0002 is going to be interesting to see moving forward. I am wondering
> how existing out-of-core extensions will react on that and if it will
> help catching up any issues. So, let's see how the experiment goes
> with HEAD on this side. Perhaps we'll have to revert 0002 at the end,
> or perhaps not...

If an extension breaks because of this, then it's doing something wrong __
Let's see what happens.

--
Sami

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Sami Imseih 2024-09-18 20:14:07 Re: query_id, pg_stat_activity, extended query protocol
Previous Message Nathan Bossart 2024-09-18 19:52:53 Re: Large expressions in indexes can't be stored (non-TOASTable)