Horton

Re: Xact end leaves CurrentMemoryContext = TopMemoryContext

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: pavel seleznev <pavel.seleznev@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2025-09-26T17:53:32Z
Lists: pgsql-hackers 
pavel seleznev <pavel.seleznev@gmail.com> writes:
> Hello,
> Should we use the same approach on line 1106 (
> https://github.com/postgres/postgres/blob/c4067383cb2c155c4cfea2351036709e2ebb3535/src/backend/libpq/hba.c#L1106
> )
> as on line 266 (
> https://github.com/postgres/postgres/blob/c4067383cb2c155c4cfea2351036709e2ebb3535/src/backend/tcop/backend_startup.c#L266
> )
> since they reference the same structure?

I see no reason to change either one.  BackendInitialize is
explicitly choosing not to run in TopMemoryContext, which is fine,
but that doesn't mean that other code has to do the same.

			regards, tom lane

Commits

  1. Split vacuumdb to create vacuuming.c/h

  2. Preserve CurrentMemoryContext across notify and sinval interrupts.

  3. Preserve CurrentMemoryContext across Start/CommitTransactionCommand.