From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Multi-xacts and our process problem |
Date: | 2015-05-11 23:18:12 |
Message-ID: | CANP8+jL-cTpJJTSv39f06ouYZJFES-QO4Rt2ERrcusKkMPWP7w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 11 May 2015 at 23:47, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> On Mon, May 11, 2015 at 03:42:26PM -0700, Joshua Drake wrote:
> > >The releases themselves are not the problem, but rather the volume of
> > >bugs and our slowness in getting additional people involved to remove
> > >data corruption bugs more quickly and systematically. Our reputation
> > >for reliability has been harmed by this inactivity.
> > >
> >
> > What I am arguing is that the release cycle is at least a big part
> > of the problem. We are trying to get so many new features that bugs
> > are increasing and quality is decreasing.
>
> Now that is an interesting observation --- are we too focused on patches
> and features to realize when we need to seriously revisit an issue?
>
I think we are unused to bugs. We have a much lower bug rate than any other
system.
I think we seriously need to review our policy of adding major new features
and have them enabled by default with no parameter to disable them. In the
early years of PostgreSQL everything had an off switch, e.g. stats,
bgwriter and even autovacuum defaulted to off for many years.
--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | David E. Wheeler | 2015-05-11 23:18:46 | Re: Fixing busted citext function declarations |
Previous Message | Tom Lane | 2015-05-11 23:04:32 | Re: Multi-xacts and our process problem |