Re: [HACKERS] Proposal: Local indexes for partitioned table

Поиск
Список
Период
Сортировка
От David Rowley
Тема Re: [HACKERS] Proposal: Local indexes for partitioned table
Дата
Msg-id CAKJS1f8SatW_D-_37yA4c4LFf79Xcmqq6uY+1oQgzCAuN806YQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] Proposal: Local indexes for partitioned table  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: [HACKERS] Proposal: Local indexes for partitioned table  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
On 18 December 2017 at 15:04, Robert Haas <robertmhaas@gmail.com> wrote:
> On Sun, Dec 17, 2017 at 5:29 AM, David Rowley
> <david.rowley@2ndquadrant.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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: Using ProcSignal to get memory context stats from a running backend
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: pg_(total_)relation_size and partitioned tables