Thread: BUG #18638: PANIC: could not open file "pg_logical/snapshots/B6-9EE5B820.snap": Permission denied

The following bug has been logged on the website:

Bug reference:      18638
Logged by:          Bhagyalaxmi R
Email address:      bhagyalaxmi.ramagalla@toyota.com
PostgreSQL version: 15.4
Operating system:   windows
Description:

Hi Team,
we have postgres servers running on windows with logical replication. But
very frequently we are observing this issue on 

"PostgreSQL 15.4 (EnterpriseDB Advanced Server 15.4.1), compiled by Visual
C++ build 1916, 64-bit"
## Log ##
024-09-27/10:2432 EDT Lod: checkpoint complete: wrote 625 buffers (110%), 0
WAL file(s) saded, 0 removed, 2 recycled, wite =59.870 5, sync=01098 s,
total: 601095 ≤ sync
2034-09-27 10:25:01 EDT PANIC: could not open file
"pg.logical/snapshots/B6-9EESB820.snap*: Permission denied
2024-09-27 10.25.01 EDT STATEMENT: START _REPLICATION SLOT "hevlassem"
LOGICAL B4/866CF008 (proto version "3', publication names "hevlasser'
2024,09-27 1025.01 EDT ERROR: replication slot "hevlassemi is active for PID
20072
2024-09-27 10.25:01 EDT STATEMENT: START_REPLICATION SLOT "hevlassem"
LOGICAL 86/9EE41BE8 (proto version '3% publication names "hevlassem"
2024-09-27 1025:02 EDT FATAL: the database system is in recovery mode

 2024-09-27 10:32:37 EDT WARNING:  PID 20760 is not a PostgreSQL backend
process
2024-09-27 10:32:42 EDT WARNING:  PID 12012 is not a PostgreSQL backend
proces

On Fri, 2024-09-27 at 15:54 +0000, PG Bug reporting form wrote:
> PostgreSQL version: 15.4
> Operating system:   windows
>
> we have postgres servers running on windows with logical replication. But
> very frequently we are observing this issue on
>
> "PostgreSQL 15.4 (EnterpriseDB Advanced Server 15.4.1), compiled by Visual
> C++ build 1916, 64-bit"

That isn't PostgreSQL; we can only help in a limited fashion.

> 2034-09-27 10:25:01 EDT PANIC: could not open file "pg.logical/snapshots/B6-9EESB820.snap*: Permission denied
> 2024-09-27 10.25.01 EDT STATEMENT: START _REPLICATION SLOT "hevlassem" LOGICAL B4/866CF008 (proto version "3',
publicationnames "hevlasser' 

Perhaps a virus scanner that messes with the data directory.

Yours,
Laurenz Albe