| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(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:49:13 |
| Message-ID: | CA+TgmoYMncgeZdTJqEBWSRAo4pCQ=4=MyrUzXvwvN5E+rTVMFA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2018-11-02 18:53:51 | Re: partitioned indexes and tablespaces |
| Previous Message | Patrick Francelle | 2018-11-02 18:41:21 | Re: Constraint documentation |