From: | Peter Geoghegan <pg(at)heroku(dot)com> |
---|---|
To: | Josh berkus <josh(at)agliodbs(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Postgres 9.6 scariest patch tournament |
Date: | 2016-04-19 19:24:01 |
Message-ID: | CAM3SWZTcCJGvxAHd9-pT8DpQVJiAk9ecZ7GT9K8tFqk6uCKMCA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Apr 18, 2016 at 1:22 PM, Josh berkus <josh(at)agliodbs(dot)com> wrote:
> We should send the owner of the scariest patch something as a prize.
> Maybe a plastic skeleton or something ...
I think it was a good idea to call it the scariest patch rather than
something more severe sounding. Having the poll only be half-serious
is a good way to avoid self-censorship, and emphasizes that we're
concerned about bugs that cause serious instability to the system as a
whole. We're less concerned about the overall number of bugs in any
given patch.
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.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2016-04-19 19:37:39 | Re: Postgres 9.6 scariest patch tournament |
Previous Message | Alvaro Herrera | 2016-04-19 18:44:36 | Re: Reducing the size of BufferTag & remodeling forks |