Re: 1.12.1 = backup ok, 1.12.2 = backup broken
От | Belbin, Peter |
---|---|
Тема | Re: 1.12.1 = backup ok, 1.12.2 = backup broken |
Дата | |
Msg-id | BCF4A499A1D8A144AF2E49797C6357110228A10079@IAMAILCLUSTER1.corp.paetec.com обсуждение исходный текст |
Ответ на | Re: 1.12.1 = backup ok, 1.12.2 = backup broken (Guillaume Lelarge <guillaume@lelarge.info>) |
Список | pgadmin-support |
Ah. Yes, the DB name had mixed case. Great! Any idea when the fix will be packaged and available? Regards, Peter. -----Original Message----- From: Guillaume Lelarge [mailto:guillaume@lelarge.info] Sent: Tuesday, January 11, 2011 4:56 PM To: Belbin, Peter Cc: 'Dave Page'; pgadmin-support@postgresql.org Subject: Re: [pgadmin-support] 1.12.1 = backup ok, 1.12.2 = backup broken Le 11/01/2011 23:29, Belbin, Peter a écrit : > [...] > I have recently switched to using 1.12.2, and found that when trying to backup a db that is remote to pgAdmin3 (runningon Windows) using default options, that I see pg_dump complaining that the server is saying there is no such database. > > I reverted back to 1.12.1, and now I am able to backup the database successfully. > > The remote pgsql instance is running 8.3.3, for what it's worth, running on solaris/sparc. > I supposed you tried to dump a database with a mixed case name or with an uppercase name? if so, this issue has already been fixed. Thanks. -- Guillaumehttp://www.postgresql.frhttp://dalibo.com
В списке pgadmin-support по дате отправления: