BUG #13702: pg_dump interprets “=” in a db name incorrectly

From: felipe(at)felipegasper(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #13702: pg_dump interprets “=” in a db name incorrectly
Date: 2015-10-23 00:34:45
Message-ID: 20151023003445.931.91267@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 13702
Logged by: Felipe Gasper
Email address: felipe(at)felipegasper(dot)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-=~!(at)#$%^&*()_+[]\{}|;:?,.<b>&lt;b&gt; 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?

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Noah Misch 2015-10-23 00:51:47 Re: Re: [BUGS] BUG #13611: test_postmaster_connection failed (Windows, listen_addresses = '0.0.0.0' or '::')
Previous Message Tom Lane 2015-10-22 23:49:29 Re: Re: [BUGS] BUG #13611: test_postmaster_connection failed (Windows, listen_addresses = '0.0.0.0' or '::')