Postgres Pro
Downloads
Home   >   mailing lists

Re: pg_dump should use current_database() instead of PQdb() - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: pg_dump should use current_database() instead of PQdb()
Date
Msg-id 39662334-ec23-d762-4711-ae5e253b119a@2ndquadrant.com
Whole thread Raw
In response to pg_dump should use current_database() instead of PQdb()  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
Tree view 
On 4/10/18 12:40, Peter Eisentraut wrote:
> A report from a pgbouncer user revealed that running pg_dump -C/--create
> does not work through a connection proxy if the virtual database name on
> the proxy does not match the real database name on the database server.
> That's because pg_dump looks up the database to be dumped using the
> information from PQdb().  It should be using current_database() instead.
>  (The code was quite likely written before current_database() was
> available (PG 7.3)).
> 
> See attached patch.

committed

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

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Proper way to reload config files in backend SIGHUP handler
Next
From: Michael Paquier
Date:
Subject: Re: Is there a memory leak in commit 8561e48?