Heikki Linnakangas 957bafb209 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:27 +02:00
..
initdb	Translation updates	2013-02-03 23:58:38 -05:00
pg_basebackup	Translation updates	2013-02-03 23:58:38 -05:00
pg_config	Translation updates	2013-02-03 23:58:38 -05:00
pg_controldata	Translation updates	2013-02-03 23:58:38 -05:00
pg_ctl	Translation updates	2013-02-03 23:58:38 -05:00
pg_dump	Fix pg_dumpall with database names containing =	2013-02-20 17:12:27 +02:00
pg_resetxlog	Translation updates	2013-02-03 23:58:38 -05:00
pgevent	Stamp copyrights for year 2011.	2011-01-01 13:18:15 -05:00
psql	Translation updates	2013-02-03 23:58:38 -05:00
scripts	Translation updates	2013-02-03 23:58:38 -05:00
Makefile	Make distprep and *clean build targets recurse into all subdirectories.	2011-07-03 13:55:27 -04:00