Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: Andrew Bille <andrewbille(at)gmail(dot)com>
Cc: Nathan Bossart <nathandbossart(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
Date: 2025-10-15 08:56:06
Message-ID: 202510150855.xloserzoobhu@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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/

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrew Bille 2025-10-15 09:10:32 Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables.
Previous Message Etsuro Fujita 2025-10-15 08:22:54 Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c