Re: Xact end leaves CurrentMemoryContext = TopMemoryContext - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Xact end leaves CurrentMemoryContext = TopMemoryContext
Date
Msg-id 4097142.1758909212@sss.pgh.pa.us
Whole thread Raw
In response to Re: Xact end leaves CurrentMemoryContext = TopMemoryContext  (pavel seleznev <pavel.seleznev@gmail.com>)
List 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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] GROUP BY ALL
Next
From: Dmitry Dolgov
Date:
Subject: Re: Changing shared_buffers without restart