Horton
Menu

Re: PQconninfo function for libpq

Peter Eisentraut <peter_e@gmx.net>

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

> and
> then plug in the exclusion of specific parameters in pg_basebackup, in
> the CreateRecoveryConf() function. pg_basebackup will of course always
> know what pg_basebackup is doing with these things.

Agreed on that in principle.

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,