Re: Xact end leaves CurrentMemoryContext = TopMemoryContext

pavel seleznev <pavel.seleznev@gmail.com>

From: pavel seleznev <pavel.seleznev@gmail.com>

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

Cc: pgsql-hackers@lists.postgresql.org

Date: 2025-09-26T17:38:43Z

Lists: pgsql-hackers

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?

Regards,
Pavel Seleznev

Commits

Split vacuumdb to create vacuuming.c/h
- c4067383cb2c 19 (unreleased) cited
Preserve CurrentMemoryContext across notify and sinval interrupts.
- 8565fb6fbb69 12.20 landed
- 5f86cd70d801 13.16 landed
- 54a7b21b3a9d 16.4 landed
- 4df767cf906d 15.8 landed
- 31f8d620b287 17.0 landed
- 1608902fc3a7 14.13 landed
Preserve CurrentMemoryContext across Start/CommitTransactionCommand.
- 1afe31f03cd2 18.0 landed