Re: WAL fsync scheduling - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: WAL fsync scheduling
Date
Msg-id 200011181852.NAA28413@candle.pha.pa.us
Whole thread Raw
In response to Re: WAL fsync scheduling  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
> Tom Lane writes:
> 
> > OK, we can probably assume that at least one of sigsuspend or sigpause
> > is available everywhere.
> 
> #ifdef HAVE_POSIX_SIGNALS should tell you.
> 
> > Now all you need is a free signal number. Unfortunately we're already
> > using both SIGUSR1 and SIGUSR2.
> 
> Maybe you could dump the old meaning SIGQUIT (externally invoked error),
> move quickdie() to SIGQUIT, and you got SIGUSR1 free.
> 
> (That would even make sense in two ways:  1) SIGQUIT would actually cause
> the guy to quit; 2) there is a correspondence between postmaster and
> postgres signals.)

Good idea.

Of course, this assumes my idea was valid.  Was it?


--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: WAL fsync scheduling
Next
From: Peter Eisentraut
Date:
Subject: Re: Re: BIT/BIT VARYING status