From: Álvaro Herrera <alvherre@kurilemu.de>
To: Andrew Bille <andrewbille@gmail.com>
Cc: Nathan Bossart <nathandbossart@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
Date: Wed, 15 Oct 2025 10:56:06 +0200
Message-ID: <202510150855.xloserzoobhu@alvherre.pgsql> (raw)
In-Reply-To: <CAJnzaryHjaF9WX0eHaKHM-DnV_5z8osC5hL9jyVeoVgjt3dXkA@mail.gmail.com>
On 2025-Oct-15, Andrew Bille wrote:
> > Is this a hypothetical problem or something you've experienced?
>
> The problem is real: when trying to rescue data from a large corrupted
> database, we couldn't wait for the index definition query for more than 3
> hours.
Maybe it'd be reasonable to start the recovery by doing VACUUM FULL of
all/some system catalogs.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
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: alvherre@kurilemu.de, andrewbille@gmail.com, nathandbossart@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
In-Reply-To: <202510150855.xloserzoobhu@alvherre.pgsql>
* 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