From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, Josh berkus <josh(at)agliodbs(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Postgres 9.6 scariest patch tournament |
Date: | 2016-04-19 20:16:37 |
Message-ID: | 20160419201637.GC6338@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Apr 19, 2016 at 04:06:55PM -0400, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> > Peter Geoghegan wrote:
> >> I would have appreciated more scope to say how confident I am in
> >> my prediction, and how scary in absolute terms I consider the
> >> scariest patches to be.
>
> > It was purposefully ambiguous. Maybe it should have been stated
> > explicitely.
>
> I was thinking about complaining that "scariest" and "most bugs" are
> not the same thing. Features you can turn off are not very scary,
> even if they're full of bugs (cough ... parallel query ... cough),
> because we could just ship 'em disabled by default until there's
> more reason to trust them. What I find scary is patches that can
> break existing use-cases with no simple workaround. I'm not sure
> which one to vote for yet.
There's space on the ballot for up to three, and it appears to be a
ranked choice or similar preference system.
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-04-19 20:48:28 | Re: [COMMITTERS] pgsql: Add trigonometric functions that work in degrees. |
Previous Message | Tom Lane | 2016-04-19 20:06:55 | Re: Postgres 9.6 scariest patch tournament |