| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | 李杰(慎追) <adger(dot)lj(at)alibaba-inc(dot)com> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, 曾文旌(义从) <wenjing(dot)zwj(at)alibaba-inc(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Subject: | Re: 回复：how to create index concurrently on partitioned table |
| Date: | 2020-06-15 12:37:42 |
| Message-ID: | 20200615123742.GL52676@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 15, 2020 at 08:15:05PM +0800, 李杰(慎追) wrote:
> As shown above, an error occurred while creating an index in the second partition.
> It can be clearly seen that the index of the partitioned table is invalid
> and the index of the first partition is normal, the second partition is invalid,
> and the Third Partition index does not exist at all.
That's a problem. I really think that we should make the steps of the
concurrent operation consistent across all relations, meaning that all
the indexes should be created as invalid for all the parts of the
partition tree, including partitioned tables as well as their
partitions, in the same transaction. Then a second new transaction
gets used for the index build, followed by a third one for the
validation that switches the indexes to become valid.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ranier Vilela | 2020-06-15 12:49:31 | Re: Postgresql13_beta1 (could not rename temporary statistics file) Windows 64bits |
| Previous Message | Michael Paquier | 2020-06-15 12:20:39 | Re: doc review for v13 |