From: Laurenz Albe <laurenz.albe@cybertec.at>
To: bhagyalaxmi.ramagalla@toyota.com
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18638: PANIC: could not open file "pg_logical/snapshots/B6-9EE5B820.snap": Permission denied
Date: Fri, 27 Sep 2024 20:00:30 +0200
Message-ID: <3f7e748610607403c134b359435a1a5134ec13cf.camel@cybertec.at> (raw)
In-Reply-To: <18638-760882b4e5851b71@postgresql.org>
References: <18638-760882b4e5851b71@postgresql.org>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: laurenz.albe@cybertec.at, bhagyalaxmi.ramagalla@toyota.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18638: PANIC: could not open file "pg_logical/snapshots/B6-9EE5B820.snap": Permission denied
In-Reply-To: <3f7e748610607403c134b359435a1a5134ec13cf.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox