Re: No Callbacks on FATAL

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: No Callbacks on FATAL
Дата
Msg-id 782965.1673486247@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: No Callbacks on FATAL  (Andres Freund <andres@anarazel.de>)
Ответы Re: No Callbacks on FATAL  (Aleksander Alekseev <aleksander@timescale.com>)
Список pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> On 2023-01-11 18:10:33 -0500, Tom Lane wrote:
>> It's intended behavior, and I seriously doubt that it ever worked
>> differently.

> Hm? MemoryContextDelete() unconditionally calls the
> callbacks. ShutdownPostgres() calls AbortOutOfAnyTransaction(). So if there's
> an ongoing transaction, we'll call the reset callbacks on TopMemoryContext and
> its children.

Hmm ... I'd forgotten that we'd reach AbortOutOfAnyTransaction in
the FATAL code path.  It does seem like any memory contexts below
TopTransactionContext ought to get cleaned up then.

As you say, we really need more details to see what's happening
here.

            regards, tom lane



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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: on placeholder entries in view rule action query's range table
Следующее
От: Peter Geoghegan
Дата:
Сообщение: Re: Reducing the WAL overhead of freezing in VACUUM by deduplicating per-tuple freeze plans