From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | "T(dot)J(dot) Adami" <adamitj(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: backup and restore |
Date: | 2008-01-16 09:34:06 |
Message-ID: | 478DCF8E.1070204@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
T.J. Adami wrote:
> On 15 jan, 12:29, d(dot)(dot)(dot)(at)archonet(dot)com (Richard Huxton) wrote:
>>> It's quite simple to have problems with pgAdmin's backup procedure.
>> Hmm - shouldn't be, and if so then please let the pgAdmin people know!
>> They're always working to improve the package and it's
>>
>
> I think the same. We (company I work for) develop an ERP software with
> more than 200 customers, and each one have a individual and
> confidential database with PostgreSQL.
> Using pgAdmin version 1.6.x or lower with those databases causes
> errors when the database is restored from a .backup file created with
> compression from pgAdmin. However, to kill the doubt, I realize those
> errors with pg_restore utility from terminal as well.
What puzzles me is that as far as I know, pgAdmin *uses* pg_dump and
pg_restore to handle its backup needs.
> P.S: I have to trace exactly these pgAdmin issues. The issues really
> exists (I'll not post any fake message here if it was not true), but I
> can't send databases dump to reproduce them according the contract
> with our customers (confidential data).
I'm sure that will be appreciated. Open source projects rely on
knowledgable users who are prepared to do a little investigating. It's
what helps drive reliability up.
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2008-01-16 09:40:39 | Re: LIKE and REGEX optimization |
Previous Message | tivvpgsqljdbc | 2008-01-16 09:30:22 | Re: Patch for Statement.getGeneratedKeys() |