| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: partitioned indexes and tablespaces |
| Date: | 2018-11-03 19:24:28 |
| Message-ID: | 20181103192428.wlbx5hcxtjn6bjd6@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2018-Nov-03, Robert Haas wrote:
> Well, you've guaranteed that already. Now 11 will be different from
> 11.1, and tables will be different from indexes until somebody goes
> and makes that consistent again.
Nobody is running 11.0 in production. The people using 11.0 are just
testing, and those that run into this behavior have already reported as
an inconvenience, not something to rely on.
> I now wish I hadn't objected to changing the behavior in April. If
> I'd know that the alternative was going to be to change it in
> November, back-patched, two days before a minor release, with more
> people voting against the change than for it, I would have kept my
> mouth shut.
Well, you didn't object to changing index behavior in April. You
objected to a change related to tables. Nobody had noticed this
behavior for indexes.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-11-03 19:30:15 | Re: partitioned indexes and tablespaces |
| Previous Message | obouda | 2018-11-03 19:19:19 | Re: backend crash on DELETE, reproducible locally |