| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: broken documentation: BackgroundWorkerInitializeConnection(NULL, NULL); |
| Date: | 2015-05-15 19:53:50 |
| Message-ID: | CA+TgmoaND7hng6F+38Jn7=iteoO4QvDxcJk9vUcC1yrtRUbsGw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-05-15 19:54:32 | Re: broken documentation: BackgroundWorkerInitializeConnection(NULL, NULL); |
| Previous Message | Stephen Frost | 2015-05-15 19:44:21 | Re: pgsql: Add pg_audit, an auditing extension |