| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Cc: | Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com>, Alexander Lakhin <exclusion(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY |
| Date: | 2025-12-07 23:29:12 |
| Message-ID: | aTYNyPELpDeNAHLc@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Dec 07, 2025 at 10:07:45PM +0100, Alvaro Herrera wrote:
> Hmm, as I recall it's quite intentional that the index on a partitioned
> table is marked !indisvalid; such indexes are only supposed to be marked
> valid once indexes on all partitions have been attached. As I recall,
> if you remove that prohibition, some pg_dump scenarios fail.
Right. If indisvalid is true on a partitioned table, then we are sure
that all its partitions have valid indexes. If indisvalid is false,
some of its partitions may have an invalid index. In the false case,
things can be a bit lossy as well. For example, an ALTER TABLE ONLY
could switch a partition's indisvalid to be true, without switching to
true the indisvalid of its partitioned table.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Previous Message | David G. Johnston | 2025-12-07 23:10:00 | Re: Fix incorrect comments in tuplesort.c |