Re: Passing current_database to BackgroundWorkerInitializeConnection - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Passing current_database to BackgroundWorkerInitializeConnection
Date
Msg-id 34B484DA-5CAA-4A99-8C91-5231F2F3383B@anarazel.de
Whole thread Raw
In response to Re: Passing current_database to BackgroundWorkerInitializeConnection  (Jeremy Finzel <finzelj@gmail.com>)
Responses Re: Passing current_database to BackgroundWorkerInitializeConnection  (Jeremy Finzel <finzelj@gmail.com>)
List pgsql-hackers

On March 30, 2018 3:16:31 PM PDT, Jeremy Finzel <finzelj@gmail.com> wrote:
>> What do you mean with "current database"? Before you
>> BackgroundWorkerInitializeConnection() there is no such thing?
>
>
>My module is based directly off the worker_spi example. The worker is
>dynamically launched via SQL command. But in the worker_spi example,
>the
>database postgres is just hardcoded as the database in which to start
>the
>background worker process. Instead, I want to start it in the database
>in
>which I run the SQL command.

The started worker isn't associated with the original database. You can pass the database oid as an argument to the
launchedbgworker. 

Andres

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


pgsql-hackers by date:

Previous
From: Jeremy Finzel
Date:
Subject: Re: Passing current_database to BackgroundWorkerInitializeConnection
Next
From: Chapman Flack
Date:
Subject: Re: [HACKERS] AdvanceXLInsertBuffer vs. WAL segment compressibility