broken documentation: BackgroundWorkerInitializeConnection(NULL, NULL); - Mailing list pgsql-hackers

From Pavel Stehule
Subject broken documentation: BackgroundWorkerInitializeConnection(NULL, NULL);
Date
Msg-id CAFj8pRBzQ1o9mkN=-iUVY8cAJp24KJTe0DuE8bSqEXXhPYY-Sw@mail.gmail.com
Whole thread Raw
Responses Re: broken documentation: BackgroundWorkerInitializeConnection(NULL, NULL);  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Hi

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

I found some older thread related to this topic

http://www.postgresql.org/message-id/13994.1376145608@sss.pgh.pa.us

Regards

Pavel

pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: KNN-GiST with recheck
Next
From: Robert Haas
Date:
Subject: Re: PATCH: pgbench allow '=' in \set