Heikki Linnakangas 79f21b3107 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:30 +02:00
..
initdb	Enable building with Microsoft Visual Studio 2012.	2013-02-06 14:56:17 -05:00
pg_basebackup	Translation updates	2013-02-04 00:01:19 -05:00
pg_config	Translation updates	2013-02-04 00:01:19 -05:00
pg_controldata	Translation updates	2013-02-04 00:01:19 -05:00
pg_ctl	Translation updates	2013-02-04 00:01:19 -05:00
pg_dump	Fix pg_dumpall with database names containing =	2013-02-20 17:12:30 +02:00
pg_resetxlog	Translation updates	2013-02-04 00:01:19 -05:00
pgevent	Run pgindent on 9.2 source tree in preparation for first 9.3	2012-06-10 15:20:04 -04:00
psql	Translation updates	2013-02-04 00:01:19 -05:00
scripts	Translation updates	2013-02-04 00:01:19 -05:00
Makefile	Update copyright notices for year 2012.	2012-01-01 18:01:58 -05:00