On 2021-Jun-22, Mike Yeap wrote: > I have a Postgres version 11.11 configured with both physical replication > slots (for repmgr) as well as some logical replication slots (for AWS > Database Migration Service (DMS)). This morning, the server went panic with > the following messages found in the log file: > > 2021-06-22 04:56:35.314 +08 [PID=19457 application="[unknown]" > user_name=dms database=** host(port)=**(48360)] PANIC: could not open file > "pg_logical/snapshots/969-FD606138.snap": Operation not permitted Hmm, isn't this strange? open(3) is not documented to return EPERM, which is what this error string maps to. You should definitely not mess with the PG data dir; if you do, it's your problem when things break. In this case you may not be messing with the data dir yourself, but perhaps you kernel is buggy or you have some security module that prevents the operation from working properly, or something. -- Álvaro Herrera Valdivia, Chile — https://www.EnterpriseDB.com/
