Re: PQconninfo function for libpq

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Boszormenyi Zoltan <zb(at)cybertec(dot)at>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PQconninfo function for libpq
Date: 2012-11-27 21:13:16
Message-ID: 50B52CEC.4000609@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2012-11-27 21:20:02 Re: PQconninfo function for libpq
Previous Message Robert Haas 2012-11-27 21:02:27 Re: MySQL search query is not executing in Postgres DB