Re: pg_dump should use current_database() instead of PQdb()

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: pg_dump should use current_database() instead of PQdb()
Дата
Msg-id 9602.1523378978@sss.pgh.pa.us
обсуждение исходный текст
Ответ на pg_dump should use current_database() instead of PQdb()  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Список pgsql-hackers
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> 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.

Looks reasonable in a quick once-over, but I've not tested it.

            regards, tom lane


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: pg_dump should use current_database() instead of PQdb()
Следующее
От: Greg Stark
Дата:
Сообщение: Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS