Postgres Pro
Downloads
Home   >   mailing lists

Thread: pgadmin3, v.1.12.3 - pgdump fails - error in arguments list

pgadmin3, v.1.12.3 - pgdump fails - error in arguments list

From
Berthold Humkamp
Date:
Hi all,

my environment is as follows:

Platform: x86_64
Distribution: gentoo - mostly stable
pgadmin3, v.1.12.3, german menus

I can't try v.1.14. beta, because it's a production server and I don't
want to install packages not delivered by gentoo-ebuilds

When calling the dump feature from pgadmin3, I get the following message:

/usr/bin/pg_dump --host localhost --port 5432 --username "postgres"
--format custom --blobs --verbose --file
"/home/bhk/pg-backup/XYZ_20110628.dump" \"XYZ\"

pg_dump: [Archivierer (DB)] Verbindung zur Datenbank »"XYZ"«
fehlgeschlagen: FATAL:  Datenbank »"XYZ"« existiert nicht
pg_dump: *** abgebrochen wegen Fehler

Prozess beendete mit Exitcode 1.


The error is from pgdump, because of the backslashes around the database
name. They shouldn't be there. The database name is XYZ and not "XYZ"

Greetings from Germany,

Berthold Humkamp

Re: pgadmin3, v.1.12.3 - pgdump fails - error in arguments list

From
Guillaume Lelarge
Date:
On Tue, 2011-06-28 at 08:57 +0200, Berthold Humkamp wrote:
> Hi all,
> 
> my environment is as follows:
> 
> Platform: x86_64
> Distribution: gentoo - mostly stable
> pgadmin3, v.1.12.3, german menus
> 
> I can't try v.1.14. beta, because it's a production server and I don't
> want to install packages not delivered by gentoo-ebuilds
> 
> When calling the dump feature from pgadmin3, I get the following message:
> 
> /usr/bin/pg_dump --host localhost --port 5432 --username "postgres"
> --format custom --blobs --verbose --file
> "/home/bhk/pg-backup/XYZ_20110628.dump" \"XYZ\"
> 
> pg_dump: [Archivierer (DB)] Verbindung zur Datenbank »"XYZ"«
> fehlgeschlagen: FATAL:  Datenbank »"XYZ"« existiert nicht
> pg_dump: *** abgebrochen wegen Fehler
> 
> Prozess beendete mit Exitcode 1.
> 
> 
> The error is from pgdump, because of the backslashes around the database
> name. They shouldn't be there. The database name is XYZ and not "XYZ"
> 

Are you sure you use 1.12.3? because this bug has been fixed in 1.12.3.
Moreover, I tried to the same thing with 1.12.3 and it works for me.


-- 
Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com