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

From Andrew Borodin
Subject Re: [HACKERS] background sessions
Date
Msg-id CAJEAwVGdvabmLCAmFexLrL9NfEfM-QumQjGQ_71b2-7D62S9AQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] background sessions  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: [HACKERS] background sessions  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
2016-12-14 20:45 GMT+05:00 Peter Eisentraut <peter.eisentraut@2ndquadrant.com>:
> On 12/11/16 5:38 AM, Andrew Borodin wrote:
>> 2. From my point of view the interface of the feature is the strong
>> point here (compared to pg_background). But it does not help
>> programmer to follow good practice: bgworker is a valuable and limited
>> resource, may be we could start session with something like
>> TryBeginSession()?
>
> What exactly would that do?
Return status (success\failure) and session object, if a function succeeded.

If there is max_connections exceeded, then (false,null).

I'm not sure whether this idiom is common for Python.

Best regards, Andrey Borodin.



pgsql-hackers by date:

Previous
From: Ian Jackson
Date:
Subject: Re: [HACKERS] [OSSTEST PATCH 0/1] PostgreSQL db: Retry on constraintviolation [and 2 more messages] [and 1 more messages]
Next
From: Vladimir Rusinov
Date:
Subject: [HACKERS] [PATCH] Remove trailing whitespaces from documentation