Re: PQconninfo function for libpq - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: PQconninfo function for libpq
Date
Msg-id 50B53184.3070304@gmx.net
Whole thread Raw
In response to Re: PQconninfo function for libpq  (Magnus Hagander <magnus@hagander.net>)
Responses Re: PQconninfo function for libpq  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On 11/27/12 4:20 PM, Magnus Hagander wrote:
> On Tue, Nov 27, 2012 at 10:13 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
>> On 11/22/12 6:44 AM, Magnus Hagander wrote:
>>> I'm thinking it might be a better idea to just have PG_CONNINFO_NORMAL
>>> and PG_CONNINFO_PASSWORD (which still make sense to separate),
>>
>> What is the use case for separating them?
> 
> Getting a connection string that doesn't contain sensitive information
> like a password. In order to show it in a dialog box, for example.

There is already the PQconninfoOption.dispchar field for this purpose.




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Bugs in CREATE/DROP INDEX CONCURRENTLY
Next
From: Peter Eisentraut
Date:
Subject: Re: MySQL search query is not executing in Postgres DB