From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Michael Meskes <meskes(at)postgresql(dot)org> |
Cc: | PostgreSQL Hacker <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [mike.aubury@aubit.com: PGconn ?] |
Date: | 2008-02-01 08:13:59 |
Message-ID: | 20021.1201853639@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Michael Meskes <meskes(at)postgresql(dot)org> writes:
> From: Mike Aubury <mike(dot)aubury(at)aubit(dot)com>
> Any chance of adding this (or something similar) for the next RC?
> I don't like the idea of adding a feature albeit a very small one to 8.3
> at this point in time without even a small discussion. Mike explained to
> me that he needs to access the PGconn structure of the current
> connection. He used to get it by using an undocumented but exported
> internal function in libecpg. However, with us cleaning up the namespace
> this function now disappeared and I refused to reactivate it because it
> only gave a pointer to an undocumented internal structure. However, the
> approach he's proposing now (using the PGconn structure instead) works
> inside the documented PGSQL framework and thus whould be fine. Is it
> okay to add this to 8.3. now? Yes, I know, I need to add it to the
> export list too.
> In the long run I would like to implement whatever is missing in ecpg
> and deprecate this function, but this isn't doable for 8.3.
It's too late for 8.3 --- the tarball is already wrapped, and we won't
consider a re-wrap short of some truly sickening bug report showing up
in the next day or so.
I'd suggest thinking in terms of a proper fix for 8.4.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Gaetano Mendola | 2008-02-01 11:08:56 | Limit changes query plan |
Previous Message | Michael Meskes | 2008-02-01 08:03:10 | [mike.aubury@aubit.com: PGconn ?] |