| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Thom Brown <thom(at)linux(dot)com> |
| Cc: | 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 14:54:30 |
| Message-ID: | CA+TgmoYu3PX1LJhjo7BOJ+gR93EriD4DC+87s8QEhj6a5dUSrw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Tue, Apr 5, 2022 at 8:41 AM Thom Brown <thom(at)linux(dot)com> wrote:
> I know it's been 8 years, but I still think it would be a useful note
> to add to the docs.
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.
Also one of us will need to do s/pg_xlog/pg_wal/.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2022-04-05 14:58:43 | Re: [COMMITTERS] pgsql: Allow time delayed standbys and recovery |
| Previous Message | Robert Haas | 2022-04-05 14:51:01 | Re: API stability [was: pgsql: Fix possible recovery trouble if TRUNCATE overlaps a checkpoint.] |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2022-04-05 14:58:43 | Re: [COMMITTERS] pgsql: Allow time delayed standbys and recovery |
| Previous Message | Robert Haas | 2022-04-05 14:51:01 | Re: API stability [was: pgsql: Fix possible recovery trouble if TRUNCATE overlaps a checkpoint.] |