From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Andres Freund <andres(at)anarazel(dot)de>, 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-07 18:41:25 |
Message-ID: | CA+TgmoY+=EtDMCObQN1+WmybRaSQGoSEWO2D-sTkOjz+=9r2SA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Nov 7, 2018 at 1:22 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> > But maybe you've adopted that policy already. You back-patched a
> > behavior change 2 days before a minor release when the vote was 2-3
> > against the change.
>
> It was? This is my count:
> For: Alvaro, Andrew, Tom
> Against: Michael, Robert, Andres
Tom's message was posted after you had already committed it. His vote
counts from the point of view of determining retrospectively whether
your action had support, but you can't use it to justify the decision
to push the commit when you did, unless you used a time machine to
foresee his message before he posted it.
> Also, I contested every point that was raised about this patch. I don't
> think there were any remaining technical objections.
Sure, but I don't think the standard is whether you told people that
they were wrong. I think the standard is whether you convinced them
to revise their position. You sure haven't convinced me.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2018-11-07 18:49:44 | Re: Connection limit doesn't work for superuser |
Previous Message | Robert Haas | 2018-11-07 18:37:10 | Re: ATTACH/DETACH PARTITION CONCURRENTLY |