Re: Reducing WaitEventSet syscall churn - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Reducing WaitEventSet syscall churn
Date
Msg-id CA+hUKGKE=cKUChUjJqkgZUubmfBB=X8Fp+t=EDeVycLPNSEx7Q@mail.gmail.com
Whole thread Raw
In response to Re: Reducing WaitEventSet syscall churn  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers
On Fri, Jul 31, 2020 at 9:42 AM Thomas Munro <thomas.munro@gmail.com> wrote:
> On Thu, Jul 30, 2020 at 5:50 PM Thomas Munro <thomas.munro@gmail.com> wrote:
> > I pushed those three patches, but will wait for more discussion on the rest.
>
> And here's a rebase, to make cfbot happy.

And again.

To restate the two goals of the remaining patches:

1.  Use FeBeWaitSet for walsender, instead of setting up and tearing
down temporary WaitEventSets all the time.
2.  Use the standard WL_EXIT_ON_PM_DEATH flag for FeBeWaitSet, instead
of the special case ereport(FATAL, ... "terminating connection due to
unexpected postmaster exit" ...).

For point 2, the question I am raising is: why should users get a
special FATAL message in some places and not others, for PM death?
However, if people are attached to that behaviour, we could still
achieve goal 1 without goal 2 by handling PM death explicitly in
walsender.c and I'd be happy to post an alternative patch set like
that.

Attachment

pgsql-hackers by date:

Previous
From: vignesh C
Date:
Subject: Re: Parallel Inserts in CREATE TABLE AS
Next
From:
Date:
Subject: RE: [PATCH] Feature improvement for CLOSE, FETCH, MOVE tab completion