| From: | Andrew Bille <andrewbille(at)gmail(dot)com> |
|---|---|
| To: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| 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 09:10:32 |
| Message-ID: | CAJnzarxfQMYjshV3iHp2vizOJx8oPxYEqsWDzVgQJgQq=-WDNA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Thank you, that case has already been resolved, and the data has been
recovered.
System reindex and vacuum full didn't help.
The schema and indexes were not needed, a modified pg_dump helped us.
On Wed, Oct 15, 2025 at 3:56 PM Álvaro Herrera <alvherre(at)kurilemu(dot)de> wrote:
> 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/
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yuri Zamyatin | 2025-10-15 14:21:29 | Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade |
| Previous Message | Álvaro Herrera | 2025-10-15 08:56:06 | Re: BUG #19086: pg_dump --data-only selects and do not uses index definitions for the dumped tables. |