Re: broken documentation: BackgroundWorkerInitializeConnection(NULL, NULL);

On Fri, May 15, 2015 at 3:53 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Thu, May 14, 2015 at 8:25 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>> The documentation (or this feature) is broken still
>>
>> If dbname is NULL or dboid is InvalidOid, the session is not connected to
>> any particular database, but shared catalogs can be accessed. If username is
>> NULL or useroid is InvalidOid, the process will run as the superuser created
>> during initdb. A background worker can only call one of these two functions,
>> and only once. It is not possible to switch databases.
>>
>> But it fails with error:
>>
>> FATAL: database 0 does not exist
>
> Ugh. I think that's a bug.
>
> Patch attached.
>
> The test code I used to verify that this works is also attached.
>
> If there are no objections, I will commit and back-patch.

Oops. Really attached this time.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company