Re: pg_rewind fails if there is a read only file.
От | Andrew Dunstan |
---|---|
Тема | Re: pg_rewind fails if there is a read only file. |
Дата | |
Msg-id | bac21305-58eb-a296-3be7-5a96c4d33b12@dunslane.net обсуждение исходный текст |
Ответ на | Re: pg_rewind fails if there is a read only file. (Laurenz Albe <laurenz.albe@cybertec.at>) |
Ответы |
Re: pg_rewind fails if there is a read only file.
|
Список | pgsql-hackers |
On 5/25/21 9:38 AM, Laurenz Albe wrote: > 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). > Perhaps we should add that read-only files can be particularly problematic. cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: