| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | sergey(dot)belyashov(at)gmail(dot)com |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17756: Invalid replica indentity set order in a dump |
| Date: | 2023-01-20 15:42:10 |
| Message-ID: | 429827.1674229330@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> Some database have a partitioned table with unique index used as REPLICA
> IDENTITY. pg_dump places ALTER TABLE tbl REPLICA IDENTITY USING INDEX
> some_idx after partial index creation. But Postgresql fails to restore such
> dump because replica identity cannot be set on invalid index some_idx:
> partition indices are not created.
Please provide a concrete example, preferably a SQL script to create
a database that triggers the problem. There are enough variables
here that nobody is likely to be excited about trying to reverse-
engineer a test case from only this amount of detail.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-01-20 17:19:15 | Re: BUG #17755: database queries get stuck for certain IDs |
| Previous Message | hubert depesz lubaczewski | 2023-01-20 14:42:10 | Re: ST_Union(rast, uniontype) treat bands with different classes as the same as first band |