| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Michael Meskes <meskes(at)postgresql(dot)org> |
| Cc: | 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 16:49:48 |
| Message-ID: | 47EA7EAC.5060605@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Michael Meskes wrote:
>
>> 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.
>
>
>
Arguably, it is aubit that is/was buggy in relying on the undocumented
"feature".
I don't think this particular change poses a great danger, but I do
think it's a bad precedent.
Anyway, I've said my piece, and don't want to take it further.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-03-26 17:16:31 | Re: Re: [COMMITTERS] pgsql: Strengthen warnings about using pg_dump's -i option. |
| Previous Message | Bruce Momjian | 2008-03-26 16:45:18 | Re: [COMMITTERS] pgsql: Strengthen warnings about using pg_dump's -i option. |