From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Michael Paquier <michael(at)paquier(dot)xyz>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: partitioned indexes and tablespaces |
Date: | 2018-11-02 18:53:51 |
Message-ID: | 20181102185351.nyik7c75lzfqjwog@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2018-Nov-02, Robert Haas wrote:
> On Fri, Nov 2, 2018 at 12:05 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> > On 2018-Nov-02, Robert Haas wrote:
> > > I strongly object to inserting behavior changes into released branches
> > > on the grounds that the behavior wasn't considered carefully enough
> > > before feature freeze.
> >
> > I'm not proposing to change any stable behavior. The thing I'm
> > proposing to change clearly cannot be used by anyone, because it just
> > throws errors.
>
> I don't get it. If the default tablespace for partition is set as for
> a regular table, that is a usable behavior. If it is taken from the
> parent table, that is a different and also usable behavior. Isn't
> this part of what you are proposing to change?
In this thread I'm not proposing to change the behavior for tables, only
for indexes. If people want to change behavior for tables (and I agree
with doing so), they can start their own threads.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2018-11-02 19:34:50 | Re: WIP Patch: Add a function that returns binary JSONB as a bytea |
Previous Message | Robert Haas | 2018-11-02 18:49:13 | Re: partitioned indexes and tablespaces |