Re: [COMMITTERS] pgsql: Allow time delayed standbys and recovery

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Thom Brown <thom(at)linux(dot)com>, Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Allow time delayed standbys and recovery
Date: 2022-04-05 15:01:56
Message-ID: CA+TgmobCYMDk-YHjG-br9_YH179enxajM969CTpG4DyFQ=kSPQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Tue, Apr 5, 2022 at 10:58 AM Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> Makes sense. I will do this soon if nobody objects.
>>
>> I'm mildly uncomfortable with the phrase "WAL records generated over
>> the delay period" because it seems a bit imprecise, but I'm not sure
>> what would be better and I think the meaning is clear.
>
> Maybe "during" instead of "over"? But I'm not sure that's the part you're referring to?

Yeah, something like that, maybe.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Geoghegan 2022-04-05 16:45:23 pgsql: Have VACUUM warn on relfrozenxid "in the future".
Previous Message Magnus Hagander 2022-04-05 14:58:43 Re: [COMMITTERS] pgsql: Allow time delayed standbys and recovery

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2022-04-05 15:05:46 Re: Mark all GUC variable as PGDLLIMPORT
Previous Message Magnus Hagander 2022-04-05 14:58:43 Re: [COMMITTERS] pgsql: Allow time delayed standbys and recovery