Postgres Pro
Downloads
Home   >   mailing lists

Re: DSM segment handle generation in background workers - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: DSM segment handle generation in background workers
Date
Msg-id CAEepm=1oRxe3n3a6bq23-2MQTSWagHTghPbpGJ1YcZEyZ_KWQA@mail.gmail.com
Whole thread Raw
In response to DSM segment handle generation in background workers  (Thomas Munro <thomas.munro@enterprisedb.com>)
Responses Re: DSM segment handle generation in background workers  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: DSM segment handle generation in background workers  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
On Mon, Oct 8, 2018 at 1:17 AM Thomas Munro
<thomas.munro@enterprisedb.com> wrote:
> That's because the bgworker startup path doesn't contain a call to
> srandom(...distinguishing stuff...), unlike BackendRun().  I suppose
> do_start_bgworker() could gain a similar call... or perhaps that call
> should be moved into InitPostmasterChild().  If we put it in there
> right after MyStartTime is assigned a new value, we could use the same
> incantation that PostmasterMain() uses.
>
> I noticed that the comment in PostmasterMain() refers to
> PostmasterRandom(), which is gone.

Maybe something like this?

-- 
Thomas Munro
http://www.enterprisedb.com
Attachment

pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Relax transactional restrictions on ALTER ENUM ... ADD TYPE (redux)
Next
From: Tom Lane
Date:
Subject: Re: Allowing printf("%m") only where it actually works