Re: Multi-xacts and our process problem - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Multi-xacts and our process problem
Date
Msg-id CANP8+jL-cTpJJTSv39f06ouYZJFES-QO4Rt2ERrcusKkMPWP7w@mail.gmail.com
Whole thread Raw
In response to Re: Multi-xacts and our process problem  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Multi-xacts and our process problem  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
On 11 May 2015 at 23:47, Bruce Momjian <bruce@momjian.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/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Multi-xacts and our process problem
Next
From: "David E. Wheeler"
Date:
Subject: Re: Fixing busted citext function declarations