broken documentation: BackgroundWorkerInitializeConnection(NULL, NULL);

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: broken documentation: BackgroundWorkerInitializeConnection(NULL, NULL);
Date: 2015-05-14 12:25:10
Message-ID: CAFj8pRBzQ1o9mkN=-iUVY8cAJp24KJTe0DuE8bSqEXXhPYY-Sw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-05-14 14:00:47 Re: PATCH: pgbench allow '=' in \set
Previous Message Alexander Korotkov 2015-05-14 10:43:22 Re: KNN-GiST with recheck