Re: pg_rewind fails if there is a read only file.

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Paul Guo <paulguo(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>
Subject: Re: pg_rewind fails if there is a read only file.
Date: 2021-05-25 13:38:55
Message-ID: 2c455145dcc27d59f66eeeb17cb8f002fa56bf06.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 2021-05-25 at 16:57 +0800, Paul Guo wrote:
> > You seem to have missed my point completely. The answer to this problem
> > IMNSHO is "Don't put a read-only file in the data directory".
>
> Oh sorry. Well, if we really do not want this we may want to document this
> and keep educating users, but meanwhile probably the product should be
> more user friendly for the case, especially considering
> that we know the fix would be trivial and I suspect it is inevitable that some
> extensions put some read only files (e.g. credentials files) in pgdata.

Good idea. I suggest this documentation page:
https://www.postgresql.org/docs/current/creating-cluster.html

Perhaps something along the line of:

It is not supported to manually create, delete or modify files in the
data directory, unless they are configuration files or the documentation
explicitly says otherwise (for example, <file>recovery.signal</file>
for archive recovery).

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavan Deolasee 2021-05-25 14:03:31 Re: Assertion failure while streaming toasted data
Previous Message Alvaro Herrera 2021-05-25 13:38:31 Re: Refactor "mutually exclusive options" error reporting code in parse_subscription_options