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

From Thomas Munro
Subject Re: Reducing WaitEventSet syscall churn
Date
Msg-id CA+hUKG+zCNJZBXcURPdQvdY-tjyD0y7Li2wZEC6XChyUej1S5w@mail.gmail.com
Whole thread Raw
In response to Reducing WaitEventSet syscall churn  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: Reducing WaitEventSet syscall churn  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers
On Tue, Jan 21, 2020 at 1:45 PM Thomas Munro <thomas.munro@gmail.com> wrote:
> Here are some patches to get rid of frequent system calls.

Here is one more case that I was sitting on because I wasn't sure how
to do it: walreceiver.c.  To make that work, libpq needs to be able to
tell you when the socket has changed, which I did with a counter that
is exposed to client code in patch 0004.  The walreceiver change in
0005 works (trace the system calls on walreceiver to see the
difference), but perhaps we can come up with a better way to code it
so that eg logical/worker.c doesn't finish up duplicating the logic.
Thoughts?

Attachment

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: pg_basebackup and snapshots
Next
From: Stephen Frost
Date:
Subject: Re: pg_basebackup and snapshots