| From: | Andrew Borodin <borodin(at)octonica(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: background sessions |
| Date: | 2016-12-14 16:33:28 |
| Message-ID: | CAJEAwVGdvabmLCAmFexLrL9NfEfM-QumQjGQ_71b2-7D62S9AQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2016-12-14 20:45 GMT+05:00 Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vladimir Rusinov | 2016-12-14 16:42:12 | [PATCH] Remove trailing whitespaces from documentation |
| Previous Message | Ian Jackson | 2016-12-14 16:20:44 | Re: [OSSTEST PATCH 0/1] PostgreSQL db: Retry on constraint violation [and 2 more messages] [and 1 more messages] |