Re: New features for pgbench

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Neil Conway <neilc(at)samurai(dot)com>, Greg Smith <gsmith(at)gregsmith(dot)com>, pgsql-patches(at)postgresql(dot)org
Subject: Re: New features for pgbench
Date: 2007-02-12 05:21:22
Message-ID: 22671.1171257682@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> Neil Conway wrote:
>> On Sun, 2007-02-11 at 23:12 -0500, Tom Lane wrote:
>>> No, it isn't. This is *not* a candidate for back-porting.
>>
>> Why is that? It seems to me that the potential downside is essentially
>> zero. This is a developer-oriented benchmark tool, after all.

> To me, it is a clear line. Once we accept for one, we may accept for
> another.

It's a new feature and we don't do new features in back branches.
I don't see that that rule is any weaker for contrib than elsewhere.
(Since the buildfarm fired up, there is no longer any meaningful
difference between contrib and core as far as quality requirements
go: you break contrib, you've broken the build.)

Possibly there would be exceptional cases where we'd allow it, but
certainly not for a patch that came in over the transom and hasn't
garnered any community consensus that it is an essential thing to have.

regards, tom lane

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message NikhilS 2007-02-12 06:47:17 Re: New features for pgbench
Previous Message Greg Smith 2007-02-12 04:57:48 Re: New features for pgbench