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

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: bhagyalaxmi(dot)ramagalla(at)toyota(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18638: PANIC: could not open file "pg_logical/snapshots/B6-9EE5B820.snap": Permission denied
Date: 2024-09-27 18:00:30
Message-ID: 3f7e748610607403c134b359435a1a5134ec13cf.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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', publication names "hevlasser'

Perhaps a virus scanner that messes with the data directory.

Yours,
Laurenz Albe

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2024-09-27 23:33:46 BUG #18639: Unexpected behavior with SET ROLE and CREATE ROLE interaction
Previous Message PG Bug reporting form 2024-09-27 15:54:40 BUG #18638: PANIC: could not open file "pg_logical/snapshots/B6-9EE5B820.snap": Permission denied