From: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Maksim Milyutin <milyutinma(at)gmail(dot)com> |
Subject: | Re: [HACKERS] Proposal: Local indexes for partitioned table |
Date: | 2017-12-18 02:38:45 |
Message-ID: | CAKJS1f8SatW_D-_37yA4c4LFf79Xcmqq6uY+1oQgzCAuN806YQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 18 December 2017 at 15:04, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Sun, Dec 17, 2017 at 5:29 AM, David Rowley
> <david(dot)rowley(at)2ndquadrant(dot)com> wrote:
>> I'm now not that clear on what the behaviour is if the ONLY keyword is
>> not specified on the CREATE INDEX for the partitioned index. Does that
>> go and create each leaf partition index regardless of if there is a
>> suitable candidate to ATTACH?
>
> No, the other way around. ONLY is being proposed as a way to create
> an initially-not-valid parent to which we can then ATTACH
> subsequently-created child indexes. But because we will have REPLACE
> rather than DETACH, once you get the index valid it never goes back to
> not-valid.
I understand what the ONLY is proposed to do. My question was in
regards to the behaviour without ONLY.
--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2017-12-18 02:51:21 | Re: pg_(total_)relation_size and partitioned tables |
Previous Message | Robert Haas | 2017-12-18 02:05:55 | Re: Using ProcSignal to get memory context stats from a running backend |