Re: Ignore 2PC transaction GIDs in query jumbling

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: Ignore 2PC transaction GIDs in query jumbling
Дата
Msg-id ZOBJdHWVoKhuYErB@paquier.xyz
обсуждение исходный текст
Ответ на Re: Ignore 2PC transaction GIDs in query jumbling  (Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>)
Ответы Re: Ignore 2PC transaction GIDs in query jumbling  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-hackers
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.
And pgbouncer may also use both of them, actually?  (Somebody, please
correct me here if necessary.)

> this seems like a reasonable way to do it unless we want to invent a
> query_jumble_ignore_unless_null attribute (which seems like overkill for
> this one case).

I don't really want to have a NULL-based property for that :)
--
Michael

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: pg_upgrade fails with in-place tablespace
Следующее
От: Pavel Stehule
Дата:
Сообщение: Re: [17] Special search_path names "!pg_temp" and "!pg_catalog"