Re: Using condition variables to wait for checkpoints - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Using condition variables to wait for checkpoints
Date
Msg-id CA+hUKGJow7rStCi6Wm4GZL_AvqnqbjKqCFbbXHHoRvx_gNz21Q@mail.gmail.com
Whole thread Raw
In response to Re: Using condition variables to wait for checkpoints  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Using condition variables to wait for checkpoints
List pgsql-hackers
On Thu, Mar 14, 2019 at 1:15 AM Robert Haas <robertmhaas@gmail.com> wrote:
> On Tue, Mar 12, 2019 at 7:12 PM Andres Freund <andres@anarazel.de> wrote:
> > Having useful infrastructure is sure cool.
>
> Yay!

+1

I renamed the CVs because the names I had used before broke the
convention that variables named ckpt_* are protected by ckpt_lck, and
pushed.

There are some other things like this in the tree (grepping for
poll/pg_usleep loops finds examples in xlog.c, standby.c, ...).  That
might be worth looking into.

-- 
Thomas Munro
https://enterprisedb.com


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Add support for hyperbolic functions, as well as log10().
Next
From: Peter Eisentraut
Date:
Subject: Re: REINDEX CONCURRENTLY 2.0