Re: [HACKERS] background sessions - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] background sessions
Date
Msg-id 7e3d0f47-ebe6-7e06-04df-f4cc3ec1d8e2@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] background sessions  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: [HACKERS] background sessions  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
On 3/8/17 14:22, Pavel Stehule wrote:
> 1. will be background session process closed automatically when parent
> process is closed?

If the communications queue goes away the process will eventually die.
This is similar to how a backend process will eventually die if the
client goes away.  Some more testing would be good here.

> 2. what timeouts are valid for this process - statement timeout, idle in
> transaction timeout 

Those should work the same way.  It's the same code that runs the
queries, starts/stops transactions, etc.

> I see significant risk on leaking sessions.

Yeah, that's a valid concern.  But I think it works ok.

> There can be more doc and examples in plpython doc. It will be main
> interface for this feature. Mainly about session processing.

OK, I'll look into that again.

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



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Enabling replication connections by default inpg_hba.conf
Next
From: Alexander Korotkov
Date:
Subject: Re: [HACKERS] [PATCH] kNN for SP-GiST