Re: problem with backup and restore (probaly stupit newb thing)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Richard Huxton <dev(at)archonet(dot)com>
Cc: Joel Fradkin <jfradkin(at)wazagua(dot)com>, pgsql-sql(at)postgresql(dot)org
Subject: Re: problem with backup and restore (probaly stupit newb thing)
Date: 2005-02-03 18:16:41
Message-ID: 17474.1107454601@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Richard Huxton <dev(at)archonet(dot)com> writes:
> Joel Fradkin wrote:
>> ServerVersion: 07.03.0200 PostgreSQL 7.4.6 on i386-redhat-linux-gnu,
>> compiled by GCC i386-redhat-linux-gcc (GCC) 3.4.2 20041017 (Red Hat 3.4.2

> OK - let's start here. The syntax here is fine, I just tested it on an
> 8.0 database. Are you sure the DB you are restoring to is version 8?

Looks to me like he's trying to use 8.0 pg_dump/pg_restore to reload
into a 7.4 server. This definitely won't work without specifying
--disable-dollar-quoting to pg_dump; and if you care about restoring
object ownership correctly, also --use-set-session-authorization.
I don't recall if there are any other gotchas.

The unicode issue I'm not sure about. Perhaps the original database was
SQL_ASCII encoding and so was allowed to contain byte sequences that
aren't legal unicode?

regards, tom lane

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Michael Fuhr 2005-02-03 19:00:38 Re: plpgsql functions to 'C' functions
Previous Message PFC 2005-02-03 18:15:04 Re: PL/PgSQL - returning multiple columns ...