| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Michael Banck <michael(dot)banck(at)credativ(dot)de>, Paul Guo <pguo(at)pivotal(dot)io>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Two fsync related performance issues? |
| Date: | 2020-12-03 06:10:38 |
| Message-ID: | CAMsr+YE-iMNXPcqeb3XEewdvttpJ7O1hdMTRJVoL+qCFmx1u3A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2 Dec 2020 at 15:41, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> On Tue, Dec 01, 2020 at 07:39:30PM +0800, Craig Ringer wrote:
> > On Wed, 14 Oct 2020, 13:06 Michael Paquier, <michael(at)paquier(dot)xyz> wrote:
> >> Yeah, it is safer to assume that it is the responsability of the
> >> backup tool to ensure that because it could be possible that a host is
> >> unplugged just after taking a backup, and having Postgres do this work
> >> at the beginning of archive recovery would not help in most cases.
> >
> > Let's document that assumption in the docs for pg_basebackup and the file
> > system copy based replica creation docs. With a reference to initdb's
> > datadir sync option.
>
> Do you have any suggestion about that, in the shape of a patch perhaps?
>
I'll try to get to that, but I have some other docs patches outstanding
that I'd like to resolve first.
--
Craig Ringer http://www.2ndQuadrant.com/
2ndQuadrant - PostgreSQL Solutions for the Enterprise
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2020-12-03 06:13:41 | Re: Printing LSN made easy |
| Previous Message | Craig Ringer | 2020-12-03 06:01:16 | Re: [PATCH] Runtime control of CLOBBER_CACHE_ALWAYS |