Re: Using condition variables to wait for checkpoints

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Using condition variables to wait for checkpoints
Date: 2019-03-13 22:05:25
Message-ID: CA+hUKGJow7rStCi6Wm4GZL_AvqnqbjKqCFbbXHHoRvx_gNz21Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 14, 2019 at 1:15 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Tue, Mar 12, 2019 at 7:12 PM Andres Freund <andres(at)anarazel(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2019-03-13 22:10:09 Re: REINDEX CONCURRENTLY 2.0
Previous Message Tom Lane 2019-03-13 21:56:32 Re: pgsql: Add support for hyperbolic functions, as well as log10().