Re: pg_stat_get_replication_slot and pg_stat_get_subscription_worker incorrectly marked as proretset

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: pg_stat_get_replication_slot and pg_stat_get_subscription_worker incorrectly marked as proretset
Дата
Msg-id Yhcml0fPu3COM78n@paquier.xyz
обсуждение исходный текст
Ответ на Re: pg_stat_get_replication_slot and pg_stat_get_subscription_worker incorrectly marked as proretset  (Amit Kapila <amit.kapila16@gmail.com>)
Ответы Re: pg_stat_get_replication_slot and pg_stat_get_subscription_worker incorrectly marked as proretset  (Amit Kapila <amit.kapila16@gmail.com>)
Список pgsql-hackers
On Wed, Feb 23, 2022 at 09:52:02AM +0530, Amit Kapila wrote:
> Thanks, so you are okay with me pushing that patch just to HEAD.

Yes, I am fine with that.  I am wondering about patching the second
function though, to avoid any risk of forgetting it, but I am fine to
leave that to your judgement.

> We don't want to backpatch this to 14 as this is a catalog change and
> won't cause any user-visible issue, is that correct?

Yup, that's a HEAD-only cleanup, I am afraid.
--
Michael

Вложения

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

Предыдущее
От: Kyotaro Horiguchi
Дата:
Сообщение: Re: Patch a potential memory leak in describeOneTableDetails()
Следующее
От: Sadhuprasad Patro
Дата:
Сообщение: Re: Per-table storage parameters for TableAM/IndexAM extensions