| From: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> | 
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> | 
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> | 
| Subject: | Re: No mention of no CIC support for partitioned index in docs | 
| Date: | 2019-06-06 00:41:03 | 
| Message-ID: | CAKJS1f9PV4WrOLUn48qe6FNTqgAeE+44F2qcT7P4q1Mknay7aA@mail.gmail.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
On Wed, 5 Jun 2019 at 08:10, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
>
> On 2019-May-24, David Rowley wrote:
>
> > It appears there is no mention of lack of support for CREATE INDEX
> > CONCURRENTLY on partitioned index in the documents.
>
> I'll leave this one for you to handle, thanks.
Thanks. I've just pushed something.
I ended up deciding that we owe the user a bit more of an explanation
of how they might work around the problem.  Of course, a partitioned
table index build is likely to take much longer than an index build on
a normal table, since most likely a partitioned table is larger. So I
went on to explain how they might minimise the time where writers will
be blocked by creating indexes concurrently on each partition first.
-- 
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2019-06-06 00:45:09 | Re: Top-N sorts in EXPLAIN, row count estimates, and parallelism | 
| Previous Message | Dave Cramer | 2019-06-05 23:05:05 | Re: Binary support for pgoutput plugin |