Re: partitioned indexes and tablespaces - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: partitioned indexes and tablespaces
Date
Msg-id 20181102185351.nyik7c75lzfqjwog@alvherre.pgsql
Whole thread Raw
In response to Re: partitioned indexes and tablespaces  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: partitioned indexes and tablespaces  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On 2018-Nov-02, Robert Haas wrote:

> On Fri, Nov 2, 2018 at 12:05 PM Alvaro Herrera <alvherre@2ndquadrant.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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: partitioned indexes and tablespaces
Next
From: Stephen Frost
Date:
Subject: Re: WIP Patch: Add a function that returns binary JSONB as a bytea