From: | Neil Conway <neilc(at)samurai(dot)com> |
---|---|
To: | Robert Partyka <bobson(at)ares(dot)fils(dot)us(dot)edu(dot)pl> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_dump file question |
Date: | 2002-10-08 16:49:10 |
Message-ID: | 878z18q3jt.fsf@mailbox.samurai.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Partyka <bobson(at)ares(dot)fils(dot)us(dot)edu(dot)pl> writes:
> \connect template1
> .....
> CREATE USER "foo" WITH SYSID 32 PASSWORD 'bar' NOCREATEDB NOCREATEUSER;
> .....
> \connect template1 "foo"
> CREATE DATABASE "foodb" WITH TEMPLATE = template0 ENCODING = 'LATIN2';
> \connect "foodb" "foo"
>
> I think evryone see why it dont work.
Yes -- it's a known problem with 7.2 that pg_dump can create
self-inconsistent dumps. In 7.3, this specific case has been fixed:
databases are now created using CREATE DATABASE ... WITH
OWNER. However, I'm not sure if there are other, similar problems that
haven't been fixed yet.
Cheers,
Neil
--
Neil Conway <neilc(at)samurai(dot)com> || PGP Key ID: DB3C29FC
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-10-08 17:21:25 | Re: Where to call SetQuerySnapshot |
Previous Message | iafmgc | 2002-10-08 16:22:48 | genetic query optimization |