Re: pgsql: Added ECPGget_PGconn() function to ecpglib, courtesy of Mike

From: Michael Meskes <meskes(at)postgresql(dot)org>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Michael Meskes <meskes(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Added ECPGget_PGconn() function to ecpglib, courtesy of Mike
Date: 2008-03-26 12:35:08
Message-ID: 20080326123508.GA22949@feivel.credativ.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Tue, Mar 25, 2008 at 05:34:44PM -0400, Andrew Dunstan wrote:
> But is it OK to add a function to the library without bumping the
> version? AFAICS all you have reverted is the version bump, so we could

With most people refering to ecpg 8.3.1 (for instance) anyway I think
the risk is rather small.

> have two versions of the library with the same version number, one with
> the new function and one without - that seems somewhat undesirable.

It is indeed.

> Also, regardless of the safety or otherwise, isn't it our standard
> practice not to change anything in stable releases except for bug fixes?
> That's part of what makes Postgres so stable, in fact.

I still fail to see how this added function could pose a problem. It
does, however, fix a bug - make that a missing, undocumenterd feature -
that causes the aubit application to break.

Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes(at)jabber(dot)org
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2008-03-26 14:32:23 pgsql: Strengthen warnings about using pg_dump's -i option.
Previous Message User Dim 2008-03-26 11:07:56 prefix - prefix: Attempts to debug the invalid memory alloc request size