| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: when the startup process doesn't |
| Date: | 2021-04-21 21:04:18 |
| Message-ID: | CAOuzzgo=KMNYRxTvNGre3z=RRhAqnfHHYX9M5Lsf7g0V7umzRA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greetings,
On Wed, Apr 21, 2021 at 17:01 Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2021-04-21 16:55:28 -0400, Tom Lane wrote:
> > My concern about it was not at all about performance, but that every time
> > you write it is a new opportunity for the filesystem to lose or corrupt
> > the data.
>
> We already do, sometimes very frequent, control file updates on standbys
> to update minRecoveryLSN. I don't recall reports of that causing
> corruption issues. So I'd not be too concerned about that aspect?
Or perhaps we should consider having multiple copies..? Though I
definitely have seen missing WAL causing difficult to realize / detect
corruption more than corrupt pg_control files...
Thanks,
Stephen
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2021-04-21 21:12:39 | Re: posgres 12 bug (partitioned table) |
| Previous Message | Andres Freund | 2021-04-21 21:00:59 | Re: when the startup process doesn't |