Re: could not open file "global/pg_filenode.map": Operation not permitted
Laurenz Albe <laurenz.albe@cybertec.at>
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Nick Renders <postgres@arcict.com>, pgsql-general@lists.postgresql.org
Date: 2024-03-11T11:10:31Z
Lists: pgsql-general
On Mon, 2024-03-11 at 11:11 +0100, Nick Renders wrote: > We have several other machines with a similar setup, but this is the only server that has this issue. > > [...] Cluster A is actually a backup from another Postgres server that is restored on a > daily basis via Barman. This means that we login remotely from the Barman server over SSH, > stop cluster A's service (port 165), clear the Data folder, restore the latest back into > the Data folder, and start up the service again. > Cluster B's Data and service (port 164) remain untouched during all this time. This is > the cluster that experiences the intermittent "operation not permitted" issue. > > Over the past 2 weeks, I have suspended our restore script and the issue did not occur. > I have just performed another restore on cluster A and now cluster B is throwing errors in the log again. > > Any idea why this is happening? It does not occur with every restore, but it seems to be related anyway. I don't know Barman, but with that incomplete description anybody will have problems determining the cause. For example, how are A and B connected? Yours, Laurenz Albe
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Remove the restriction that the relmap must be 512 bytes.
- d8cd0c6c95c0 16.0 cited