|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>|
|Cc:||Peter Eisentraut <peter_e(at)gmx(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, Boszormenyi Zoltan <zb(at)cybertec(dot)at>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: PQconninfo function for libpq|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Peter Eisentraut wrote:
>> There is already the PQconninfoOption.dispchar field for this purpose.
> I had the impression that that field would go away with this patch, but
> then again it might not be worth the compatibility break. I find the
> dispchar thingy somewhat unsightly.
It is that, without a doubt, but that API has been that way longer than
any of us have been working on the code. I'm not excited about changing
it just to have an allegedly-cleaner API. And we cannot have the field
simply "go away", because it's been exposed to applications for lo these
many years, and surely some of them are using it. So in practice we'd
be maintaining both the old API and the new one.
I think we should leave it as-is until there are more reasons to change
it than seem to be provided in this thread.
regards, tom lane
|Next Message||Kyotaro HORIGUCHI||2012-11-28 02:11:39||Re: the number of pending entries in GIN index with FASTUPDATE=on|
|Previous Message||John R Pierce||2012-11-27 23:36:57||Re: MySQL search query is not executing in Postgres DB|