Re: Some vacuum & tuning help

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, shridhar_daithankar(at)persistent(dot)co(dot)in, Christopher Browne <cbbrowne(at)libertyrms(dot)info>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Some vacuum & tuning help
Date: 2003-08-06 04:45:34
Message-ID: 15808.1060145134@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

"Matthew T. O'Connor" <matthew(at)zeut(dot)net> writes:
> ... My really question
> was can I make large changes to a contrib module to a point release,
> meaning, 7.4.0 will have what is in beta, but 7.4.1 would have a much
> improved version. Does that sound possible?

For core code, the answer would be a big NYET. We do not do feature
additions in point releases, only bug fixes. While contrib code is more
under the author's control than the core committee's control, I'd still
say that you'd be making a big mistake to not follow that basic
guideline. People expect release x.y.z+1 to be the same as x.y.z except
for bug fixes. Introducing any new bugs into x.y.z+1 would cause a
large loss in your credibility.

(speaking as one who's introduced new bugs into a point-release
recently, and is still embarrassed about it, even though the intent
was only to fix older bugs...)

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Neil Conway 2003-08-06 05:35:52 Re: Some vacuum & tuning help
Previous Message Christopher Kings-Lynne 2003-08-06 04:41:06 Re: Some vacuum & tuning help