| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Adrien NAYRAT <adrien(dot)nayrat(at)anayrat(dot)info> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: ALTER INDEX ... ALTER COLUMN not present in dump |
| Date: | 2018-11-16 00:45:05 |
| Message-ID: | 20181116004505.GC6613@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Fri, Nov 16, 2018 at 07:46:01AM +0900, Michael Paquier wrote:
> Yes, that's a bug, and something that we should try to fix in v11.
Okay, here are my notes. We need to do a couple of things here:
1) Add a new join to pg_attribute in getIndexes(), then add the
information for statistics and the associated column to IndxInfo after
parsing the gathered array using parsePGArray().
2) Add the extra ALTER INDEX commands to the queries creating the
objects in dumpIndex().
3) Add a test.
A good thing is that when ALTER INDEX .. SET STATISTICS is applied on an
index of a partitioned table, the statement is not cascaded to the
existing partitions. We may want in the future to support ONLY and make
the inheritance automatic. But that's another topic, and the fix for
v11 should be chirurgical.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melanie Plageman | 2018-11-16 00:51:45 | Re: BUG #15160: planner overestimates number of rows in join when there are more than 200 rows coming from CTE |
| Previous Message | Michael Paquier | 2018-11-15 22:46:01 | Re: ALTER INDEX ... ALTER COLUMN not present in dump |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melanie Plageman | 2018-11-16 00:51:45 | Re: BUG #15160: planner overestimates number of rows in join when there are more than 200 rows coming from CTE |
| Previous Message | Justin Pryzby | 2018-11-16 00:36:57 | Re: pg11.1 jit segv |