pgsql: Fix pg_dumpall with database names containing =

Поиск
Список
Период
Сортировка
От Heikki Linnakangas
Тема pgsql: Fix pg_dumpall with database names containing =
Дата
Msg-id E1U8BNY-0008Uu-7A@gemulon.postgresql.org
обсуждение исходный текст
Ответы Re: pgsql: Fix pg_dumpall with database names containing =  (Thom Brown <thom@linux.com>)
Список pgsql-committers
Fix pg_dumpall with database names containing =

If a database name contained a '=' character, pg_dumpall failed. The problem
was in the way pg_dumpall passes the database name to pg_dump on the
command line. If it contained a '=' character, pg_dump would interpret it
as a libpq connection string instead of a plain database name.

To fix, pass the database name to pg_dump as a connection string,
"dbname=foo", with the database name escaped if necessary.

Back-patch to all supported branches.

Branch
------
REL9_1_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/957bafb2091136161cb7f1a8a56439310c6bd1b2

Modified Files
--------------
src/bin/pg_dump/pg_dumpall.c |   34 +++++++++++++++++++++++++++++++++-
1 files changed, 33 insertions(+), 1 deletions(-)


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

Предыдущее
От: Heikki Linnakangas
Дата:
Сообщение: pgsql: Don't pass NULL to fprintf, if a bogus connection string is give
Следующее
От: Heikki Linnakangas
Дата:
Сообщение: pgsql: Fix pg_dumpall with database names containing =