Heikki Linnakangas 8b4ced45ec 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.

2013-02-20 17:12:24 +02:00

..

initdb

Translation updates

2013-02-03 23:56:29 -05:00

pg_config

Translation updates

2013-02-03 23:56:29 -05:00

pg_controldata

Translation updates

2013-02-03 23:56:29 -05:00

pg_ctl

Translation updates

2013-02-03 23:56:29 -05:00

pg_dump

Fix pg_dumpall with database names containing =

2013-02-20 17:12:24 +02:00

pg_resetxlog

Translation updates

2013-02-03 23:56:29 -05:00

pgevent

Allow vpath builds and regression tests to succeed on Mingw. Backpatch to release 8.4 - earlier releases would require more changes and it's not worth the trouble.

2010-12-24 13:31:48 -05:00

psql

Translation updates

2013-02-03 23:56:29 -05:00

scripts

Translation updates

2013-02-03 23:56:29 -05:00

Makefile

Update copyright for the year 2010.

2010-01-02 16:58:17 +00:00