Re: Using WaitEventSet in the postmaster

Thomas Munro <thomas.munro@gmail.com>

From: Thomas Munro <thomas.munro@gmail.com>

To: Justin Pryzby <pryzby@telsasoft.com>

Cc: Andres Freund <andres@anarazel.de>, pgsql-hackers@postgresql.org

Date: 2022-12-07T01:13:06Z

Lists: pgsql-hackers

On Wed, Dec 7, 2022 at 2:08 PM Justin Pryzby <pryzby@telsasoft.com> wrote:
> > +             /*
> > +              * It would probably be safe to re-use the inherited signalfd since
> > +              * signalfds only see the current processes pending signals, but it
>
> I think you mean "current process's", right ?

Fixed in v5, thanks.

Commits

Remove unneeded volatile qualifiers from postmaster.c.
- 8d2c1913ed3d 16.0 landed
Fix WaitEventSetWait() buffer overrun.
- f1821b58fc8d 16.0 landed
- 8a98523a542f 15.2 landed
- 547e60b8317e 14.7 landed
- c159b0383fa6 13.10 landed
- bf388ab82850 12.14 landed
- 1b40710a8c89 11.19 landed
Refactor DetermineSleepTime() to use milliseconds.
- 5a26c7b310b6 16.0 landed
Use WaitEventSet API for postmaster's event loop.
- 7389aad63666 16.0 landed
Allow parent's WaitEventSets to be freed after fork().
- b5d0f8ec01c0 16.0 landed
Don't leak a signalfd when using latches in the postmaster.
- 1f0019de2fe3 16.0 landed
Add WL_SOCKET_ACCEPT event to WaitEventSet API.
- 30829e52ff1a 16.0 landed
From: Phil Thompson <phil@river-bank.demon.co.uk>
- d5bbe2aca55b 7.1.1 cited