From: | David Gould <daveg(at)sonic(dot)net> |
---|---|
To: | Felipe Gasper <felipe(at)felipegasper(dot)com> |
Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #13702: pg_dump interprets “=” in a db name incorrectly |
Date: | 2015-10-23 12:45:10 |
Message-ID: | 20151023054510.5b5467c6@engels |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Thu, 22 Oct 2015 20:30:20 -0500
Felipe Gasper <felipe(at)felipegasper(dot)com> wrote:
> Interesting -- also, in 9.0 I *can* do:
>
> dbname='...'
>
> … and it works. Undocumented, apparently (?), but it does the job.
>
> But, I actually have to support all the way back to 8.1, and I’m a bit
> leery of relying on undocumented (?) features for our backup
> functionality. Hopefully down the road we can just move everything to
> >=9.3, and peace and love will reign. :)
You can dump and load older version database from newer version clients.
The dbname parsing problem you are having is on the client, not the server,
so if you can arrange to take the backup with a more current client then
one of the suggestions in this thread will work for you.
-dg
--
David Gould daveg(at)sonic(dot)net
If simplicity worked, the world would be overrun with insects.
From | Date | Subject | |
---|---|---|---|
Next Message | Sergey Burladyan | 2015-10-23 14:36:15 | Re: BUG #13657: Some kind of undetected deadlock between query and "startup process" on replica. |
Previous Message | yozh.ne | 2015-10-23 10:03:39 | BUG #13708: strange behaviour instead of syntax error |