Skip site navigation (1) Skip section navigation (2)

Re: 1.12.1 = backup ok, 1.12.2 = backup broken

From: "Belbin, Peter" <Peter(dot)Belbin(at)PAETEC(dot)com>
To: 'Guillaume Lelarge' <guillaume(at)lelarge(dot)info>
Cc: 'Dave Page' <dpage(at)pgadmin(dot)org>, "pgadmin-support(at)postgresql(dot)org"<pgadmin-support(at)postgresql(dot)org>
Subject: Re: 1.12.1 = backup ok, 1.12.2 = backup broken
Date: 2011-01-11 23:06:58
Message-ID: BCF4A499A1D8A144AF2E49797C6357110228A10079@IAMAILCLUSTER1.corp.paetec.com (view raw or flat)
Thread:
Lists: 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(at)lelarge(dot)info] 
Sent: Tuesday, January 11, 2011 4:56 PM
To: Belbin, Peter
Cc: 'Dave Page'; pgadmin-support(at)postgresql(dot)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 (running on 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.


-- 
Guillaume
 http://www.postgresql.fr
 http://dalibo.com

In response to

Responses

pgadmin-support by date

Next:From: Guillaume LelargeDate: 2011-01-11 23:16:09
Subject: Re: 1.12.1 = backup ok, 1.12.2 = backup broken
Previous:From: Guillaume LelargeDate: 2011-01-11 22:56:08
Subject: Re: 1.12.1 = backup ok, 1.12.2 = backup broken

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group