Re: [HACKERS] background sessions

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: [HACKERS] background sessions
Дата
Msg-id bb7e3dc1-1cf9-a538-c883-0fe60ad14f68@2ndquadrant.com
обсуждение исходный текст
Ответ на Re: [HACKERS] background sessions  (amul sul <sulamul@gmail.com>)
Ответы Re: [HACKERS] background sessions  (Andrew Borodin <borodin@octonica.com>)
Список pgsql-hackers
On 1/3/17 1:26 AM, amul sul wrote:
> One more requirement for pg_background is session, command_qh,
> response_qh and worker_handle should be last longer than current
> memory context, for that we might need to allocate these in
> TopMemoryContext.  Please find attach patch does the same change in
> BackgroundSessionStart().

I had pondered this issue extensively.  The standard coding convention
in postgres is that the caller sets the memory context.  See the dblink
and plpython patches that make this happen in their own way.

I agree it would make sense that you either pass in a memory context or
always use TopMemoryContext.  I'm open to these ideas, but they did not
seem to match any existing usage.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



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

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: [HACKERS] [PATCH] Reload SSL certificates on SIGHUP
Следующее
От: Fabien COELHO
Дата:
Сообщение: Re: [HACKERS] proposal: session server side variables