| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | Wim Rouquart <wim(dot)rouquart(at)kbc(dot)be> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Index (primary key) corrupt? |
| Date: | 2026-03-10 14:43:45 |
| Message-ID: | CAKAnmmKwGsCtCeQ2GvDVhp9ZTjSsoZBrfe1Yw_UfcHD1u=StUw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Mar 10, 2026 at 10:24 AM Wim Rouquart <wim(dot)rouquart(at)kbc(dot)be> wrote:
> Let me get this straight, are you still contesting that the index is
> actually not part of the dumpfile and I somehow just keep on ‘missing it’?
>
That is one possibility, yes, but there are others. We just don't have
enough data. It would be great to see exactly what pg_dump is doing so we
know where the corruption/disconnect is. If you have access, could you try:
psql -c "alter system set log_statement='all' " -c "select pg_reload_conf()"
pg_dump -t bcf_work_type --schema-only > bcf.debug
psql -c "alter system reset log_statement" -c "select pg_reload_conf()"
Then send us bcf.debug as well as the Postgres logs generated during that
request?
Cheers,
Greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2026-03-10 15:09:34 | Re: Index (primary key) corrupt? |
| Previous Message | Wim Rouquart | 2026-03-10 14:24:43 | RE: Index (primary key) corrupt? |