BUG #13702: pg_dump interprets “=” in a db name incorrectly - Mailing list pgsql-bugs

From felipe@felipegasper.com
Subject BUG #13702: pg_dump interprets “=” in a db name incorrectly
Date
Msg-id 20151023003445.931.91267@wrigleys.postgresql.org
Whole thread Raw
Responses Re: [BUGS] BUG #13702: pg_dump interprets “=” in a db name incorrectly  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      13702
Logged by:          Felipe Gasper
Email address:      felipe@felipegasper.com
PostgreSQL version: Unsupported/Unknown
Operating system:   Linux
Description:

For the purposes of an administrative frontend that I help develop/maintain,
I have a database named:

--------------
abcde_1234567890-=~!@#$%^&*()_+[]\{}|;:?,.<b><b> spaces
--------------

When I try to back up this DB via pg_dump, the utility appears to split the
DB name on the “=”, thinking that it’s another command-line option.

I’ve tried passing in “--”, but no joy. I tried passing “--dbname” then the
DB name, but pg_dump doesn’t seem to accept that argument.

The only working solution I have found is to set the DB name in PGDATABASE.

I found this in 9.0.18. Maybe it’s still a problem in supported releases,
too?



pgsql-bugs by date:

Previous
From: John R Pierce
Date:
Subject: Re: PC users trying to create database
Next
From: "David G. Johnston"
Date:
Subject: Re: [BUGS] BUG #13702: pg_dump interprets “=” in a db name incorrectly