Re: WAL fsync scheduling

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Larry Rosenman <ler(at)lerctr(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WAL fsync scheduling
Date: 2000-11-18 18:51:02
Message-ID: Pine.LNX.4.21.0011181941440.1331-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.)

--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2000-11-18 18:52:03 Re: WAL fsync scheduling
Previous Message Peter Eisentraut 2000-11-18 18:26:09 Re: WAL fsync scheduling