Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY - Mailing list pgsql-hackers

From Mihail Nikalayeu
Subject Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY
Date
Msg-id CADzfLwUzCDiB57oBW2Zx+Tud=4WDCOUQhPfcnshLDccDkXdRrA@mail.gmail.com
Whole thread Raw
In response to Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY  (Alexander Lakhin <exclusion@gmail.com>)
Responses Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY
List pgsql-hackers
Hello, Alexander!

Thanks for your investigation!

I was able to reproduce it locally, not easily, but possible.

It fails with the state then we have 2 indexes (leaf_part_rri->ri_NumIndices=2) and EACH OF them have an ancestor. So, both of them are added as arbiters.

Not sure if it correct behavior or something is broken in another place.

I'll try to dive deeper a little bit later.

Best regards,
Mikhail.

 

pgsql-hackers by date:

Previous
From: Zsolt Parragi
Date:
Subject: Re: Proposal: Adding compression of temporary files
Next
From: Hannu Krosing
Date:
Subject: Re: Patch: dumping tables data in multiple chunks in pg_dump