| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, 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 05:35:52 |
| Message-ID: | 20030806053552.GA10408@home.samurai.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Wed, Aug 06, 2003 at 12:45:34AM -0400, Tom Lane wrote:
> 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.
... and since contrib packages are distributed along with PG, it would
also be a loss to PG's credibility. IMHO, core should disallow feature
additions in point releases for contrib modules, as well as the core
code, except for very unusual situations. If contrib authors don't like
this facet of our release engineering process, they can always
distribute their code via some other outlet (gborg, SF, etc.).
-Neil
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2003-08-06 06:42:33 | Re: How Many Inserts Per Transactions |
| Previous Message | Tom Lane | 2003-08-06 04:45:34 | Re: Some vacuum & tuning help |