Re: Cause of "can't wait without a PROC structure" - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Cause of "can't wait without a PROC structure"
Date
Msg-id 200209252102.g8PL22r19218@candle.pha.pa.us
Whole thread Raw
In response to Re: Cause of "can't wait without a PROC structure"  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> I said:
> > The ordering of these shutdown hooks is the reverse of the ordering
> > of the startup initialization of the modules.  It looks like we'll
> > need to rejigger the startup ordering ... and it also looks like that's
> > going to be a rather ticklish issue.  (See comments in BaseInit and
> > InitPostgres.)  Any thoughts on how to do it?
> 
> I eventually decided that the most reasonable solution was to leave the
> startup sequence alone, and fold the ProcKill and
> ShutdownBufferPoolAccess shutdown hooks together.  This is a little ugly
> but it seems to beat the alternatives.  ShutdownBufferPoolAccess was
> effectively assuming that LWLockReleaseAll was called just before it,
> so the two modules aren't really independent anyway.

I understand.  Sometimes the dependencies are too intricate to break
apart, and you just reorder them.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Cause of "can't wait without a PROC structure"
Next
From: Tom Lane
Date:
Subject: Re: Bug in PL/pgSQL GET DIAGNOSTICS?