On Wed, 15 May 2024 08:47:00 +0200
Christoph Berg wrote:
> Re: Владимир Ступин
> > Trouble solved with restarting PostgreSQL.
>
> Hi,
>
> I'm glad you solved it.
>
> My guess would be that there was something (likely a background
> worker) still connected to that database and DROP DATABASE cou
Re: Владимир Ступин
> Trouble solved with restarting PostgreSQL.
Hi,
I'm glad you solved it.
My guess would be that there was something (likely a background
worker) still connected to that database and DROP DATABASE couldn't
get the proper lock on it.
I guess there is nothing to actually fix (a
On Mon, 13 May 2024 15:26:34 +0500
Владимир Ступин wrote:
After interrupting dropdb command, database was in semi-dropped state. It's
present in output of command psql -l, but any operation with semi-dropped
database failed. For example, cannot to connect to semi-dropped database or
backup it:
On Mon, 13 May 2024 10:09:48 +0200
Christoph Berg wrote:
> Re: Vladimir Stupin
> > Package: postgresql-15
> > Version: 15.6-0+deb12u1
> >
> > dropdb on any database hangs up. pg_activity shows query DROP DATABASE
> > ; in state ProcSignalBarrier.
> >
> > I found fix for the trouble at
> > http
Re: Vladimir Stupin
> Package: postgresql-15
> Version: 15.6-0+deb12u1
>
> dropdb on any database hangs up. pg_activity shows query DROP DATABASE
> ; in state ProcSignalBarrier.
>
> I found fix for the trouble at
> https://www.postgresql.org/message-id/E1pKAd5-005BKs-Vr%40gemulon.postgresql.org
Package: postgresql-15
Version: 15.6-0+deb12u1
Severity: normal
Dear Maintainer,
dropdb on any database hangs up. pg_activity shows query DROP DATABASE
; in state ProcSignalBarrier.
I found fix for the trouble at
https://www.postgresql.org/message-id/E1pKAd5-005BKs-Vr%40gemulon.postgresql.org
6 matches
Mail list logo
