Re: Preserve attstattarget on REINDEX CONCURRENTLY
Ronan Dunklau <ronan@dunklau.fr>
From: Ronan Dunklau <ronan@dunklau.fr>
To: Michael Paquier <michael@paquier.xyz>
Cc: Tomas Vondra <tomas.vondra@enterprisedb.com>, pgsql-hackers@postgresql.org
Date: 2021-02-05T07:22:17Z
Lists: pgsql-hackers
Le vendredi 5 février 2021, 03:17:48 CET Michael Paquier a écrit : > ConstructTupleDescriptor() does not matter much, but this patch is not > acceptable to me as it touches the area of the index creation while > statistics on an index expression can only be changed with a special > flavor of ALTER INDEX with column numbers. This would imply an ABI > breakage, so it cannot be backpatched as-is. I'm not surprised by this answer, the good news is it's being back-patched. > > Let's copy this data in index_concurrently_swap() instead. The > attached patch does that, and adds a test cheaper than what was > proposed. There is a minor release planned for next week, so I may be > better to wait after that so as we have enough time to agree on a > solution. Looks good to me ! Thank you. -- Ronan Dunklau
Commits
-
Fix ORDER BY clause in new regression test of REINDEX CONCURRENTLY
- 5b2945ec0a39 12.7 landed
- c6cd20d91ce9 13.3 landed
- 4f4726005082 14.0 landed
-
Preserve pg_attribute.attstattarget across REINDEX CONCURRENTLY
- 85edb1f2615d 12.7 landed
- 849383138581 13.3 landed
- bd1208098029 14.0 landed