Horton
Menu

Re: PQconninfo function for libpq

Magnus Hagander <magnus@hagander.net>

View thread
From: Magnus Hagander <magnus@hagander.net>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Boszormenyi Zoltan <zb@cybertec.at>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2012-11-27T21:20:02Z
Lists: pgsql-hackers 
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.

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. In psql, if the is no connection object, e.g. due to a server crash,