Message-ID: <eff17df54774694c8021683d0e4de52b15868a72.camel@cybertec.at>
Subject: Re: BUG #19426: pgdump is stuck
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: deepakverma0328@gmail.com, pgsql-bugs@lists.postgresql.org
Date: Sun, 08 Mar 2026 18:58:30 +0100
In-Reply-To: <19426-477ae230ac73041e@postgresql.org>
References: <19426-477ae230ac73041e@postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.58.3 (3.58.3-1.fc43) 
MIME-Version: 1.0
Archived-At: <https://www.postgresql.org/message-id/eff17df54774694c8021683d0e4de52b15868a72.camel%40cybertec.at>
Precedence: bulk

On Sat, 2026-03-07 at 09:40 +0000, PG Bug reporting form wrote:
> The following bug has been logged on the website:
>=20
> Bug reference:      19426
> Logged by:          Deepak Verma
> Email address:      deepakverma0328@gmail.com
> PostgreSQL version: 14.18
> Operating system:   Ubuntu 14.18-0ubuntu0.22.04.1
> Description:       =20
>=20
> We are going to take dump of my AWS Ubuntu 14.18-0ubuntu0.22.04.1 on
> postgres 14.18, while taking dump it gor stuck on
> pg_dump: reading user-defined tables
> we are not able to take single table backup also as it also stuck at same
> place.
>=20
> pg_dump: last built-in OID is 16383
> pg_dump: reading extensions
> pg_dump: identifying extension members
> pg_dump: reading schemas
> pg_dump: reading user-defined tables

Start an interactive session while pg_dump is hanging and look at the line
in pg_stat_activity that belongs to the hanging pg_dump.

Perhaps a concurrent transaction is holding an ACCESS EXCLUSIVE lock on
something.  That would not be a bug.

Yours,
Laurenz Albe