Re: pg_basebackup -R

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_basebackup -R
Date: 2017-02-18 00:10:56
Message-ID: 38b5f326-efa9-ae37-22ef-93914e65e4f7@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2/15/17 10:52, Robert Haas wrote:
> Let's wait and see if anybody else has an opinion. I imagine that, as
> further libpq parameters are added, eventually this is going to get
> long and annoying enough that we want to do something about it. But
> we might not have reached that point just yet.

I was also annoyed by it when I first saw it.

I know why we have to do it, to override any libpq environment variables.

Now that I think about it some more, I think we should unset or somehow
make libpq ignore all libpq environment variables in the server
environment. Nothing good can come of using them.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2017-02-18 00:16:08 Re: [PATCH] Teach Catalog.pm how many attributes there should be per DATA() line
Previous Message Mark Dilger 2017-02-18 00:10:47 Re: pg_recvlogical.c doesn't build with --disable-integer-datetimes