Re: Reducing WaitEventSet syscall churn

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Daniel Gustafsson <daniel(at)yesql(dot)se>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Reducing WaitEventSet syscall churn
Date: 2021-03-01 03:21:53
Message-ID: CA+hUKGJPaygh-6WHEd0FnH89GrkTpVyN_ew9ckv3+nwjmLcSeg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Feb 27, 2021 at 2:48 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> Here's the alternative patch set, with no change to existing error
> message behaviour. I'm going to commit this version and close this CF
> item soon if there are no objections.

Pushed.

That leaves just walreceiver and postgres_fdw in need of WaitEventSet
improvements along these lines. The raw ingredients for that were
present in earlier patches, and I think Horiguchi-san had the right
idea: we should use the libpq event system to adjust our WES as
appropriate when it changes the socket underneath us. I will leave
this CF entry open a bit longer in case he would like to post an
updated version of that part (considering Tom's feedback[1]). If not,
we can close this and try again in the next cycle.

[1] https://www.postgresql.org/message-id/2446176.1594495351%40sss.pgh.pa.us

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Nancarrow 2021-03-01 03:38:21 Re: Parallel INSERT (INTO ... SELECT ...)
Previous Message Amit Kapila 2021-03-01 03:21:18 Re: locking [user] catalog tables vs 2pc vs logical rep