| From: | Ben Chobot <bench(at)silentmedia(dot)com> |
|---|---|
| To: | Nick Cleaton <nick(at)cleaton(dot)net> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17389: pg_repack creates race conditions on streaming replicas |
| Date: | 2022-02-01 15:25:13 |
| Message-ID: | 8cc974ce-8398-a892-a0dc-a65d5b5d65c6@silentmedia.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Nick Cleaton wrote on 2/1/22 12:43 AM:
> We've very occasionally seen something similar with a script that did
> CREATE INDEX CONCURRENTLY, RENAME INDEX and DROP INDEX CONCURRENTLY on
> the primary, but not since we upgraded from 9.4 to 12 and switched to
> using REINDEX CONCURRENTLY. In our case the OID in the error belonged
> to the index that was dropped, not the table.
>
> I think It'd be worth noting the OIDs of the table and its indexes
> before each run, so that you can tell if it belongs to an index in
> your case.
Oh it most certainly did. (We validated it in other testing, and the
test we ran had pg_repack only working on indices anyway.)
It's good to hear you don't see any such issues using SQL commands. Have
you tried using a simple REINDEX CONCURRENTLY?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-02-01 15:47:12 | Re: BUG #17390: Function, to_date() -- unexpected values and a request |
| Previous Message | Etsuro Fujita | 2022-02-01 08:59:41 | Re: BUG #17355: Server crashes on ExecReScanForeignScan in postgres_fdw when accessing foreign partition |