Re: Order of operations in SubPostmasterMain()

From: Greg Stark <stark(at)mit(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Order of operations in SubPostmasterMain()
Date: 2016-09-29 20:05:05
Message-ID: CAM-w4HPEK01i6HFN5reT=azFJYsfLLUsTZa-783_Q6EKCfAmjg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Sep 29, 2016 at 8:46 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> We could probably refactor things enough so that we do pq_init()
> before PGSharedMemoryReAttach(). It would be a little bit ugly,
> and it would fractionally increase the chance of a reattach failure
> because pq_init() palloc's a few KB worth of buffers. I'm not quite
> sure if it's worth it; thoughts? In any case the mentioned comments
> are obsolete and need to be moved/rewritten.

Just speaking off the cuff without reviewing the code in detail...

Alternately we could call pq_init in the error path if it hasn't been
called yet. I'm sure there are problems with doing that in general but
for the specific errors that can happen before pq_init it might be
feasible since they obviously can't have very much shared state yet to
have corrupted.

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2016-09-29 20:11:19 Re: pg_basebackup, pg_receivexlog and data durability
Previous Message Peter Eisentraut 2016-09-29 20:02:06 Re: pageinspect: Hash index support