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

From amul sul
Subject Re: [HACKERS] background sessions
Date
Msg-id CAAJ_b97fqGXAFkovxc+750tMziRoFaqGFL4weU7Hr01EgCNJJw@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] background sessions  (Andrew Borodin <borodin@octonica.com>)
List pgsql-hackers
On Thu, Dec 15, 2016 at 12:24 PM, Andrew Borodin <borodin@octonica.com> wrote:
> 2016-12-15 0:30 GMT+05:00 Peter Eisentraut <peter.eisentraut@2ndquadrant.com>:
>>>>> 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.
>>
>> You can catch PostgreSQL exceptions in PL/Python, so this can be handled
>> in user code.
>>
>> Some better connection management or pooling can probably be built on
>> top of the primitives later, I'd say.
>
> Agree, doing this in Python is the better option.
>
> And one more thing... Can we have BackgroundSessionExecute() splitted
> into two parts: start query and wait for results?
> It would allow pg_background to reuse bgsession's code.
>
+1

Regards,
Amul



pgsql-hackers by date:

Previous
From: Andrew Borodin
Date:
Subject: Re: [HACKERS] background sessions
Next
From: Craig Ringer
Date:
Subject: [HACKERS] bigint vs txid user confusion