From: Oleg Lebedev <olebedev@waterford.org>
To: Postgres SQL Mailing List <pgsql-sql@postgresql.org>
Subject: Re: pg_dumpall
Date: Tue, 14 May 2002 16:15:00 -0600
Message-ID: <3CE18C64.B2EEB710@waterford.org> (raw)
References: <3CE02FF5.ABDC8CC@waterford.org>
I figured it out.
It seems like I had a view VA defined in database A, which extracted data
from the table TA. I had to drop and recreate the table, so VA was
referencing the old table A. After that I exported data using dump_all. This
explains why psql wouldn't create view VA when importing data from a file
created by dump_all.
Is there a way to update all derived views when a table is dropped and then
created again?
thanks,
Oleg
> Hello,
> I am upgrading from Postgres7.1.3 to Postgres7.2.1 and dumped all the
> data to a file with
> pg_dumpall -o > dump
> When I go throught the dump file it turns out that some views are
> created before the base relations are created. When I try to import the
> dump file in Postgres 7.2.1 some of the views are not created because if
> this.
> Why the order of created data objects is wrong?
> I kept view definitions in several files, but I would still like to know
> how to move data between releases consistently.
> thanks,
>
> Oleg
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: olebedev@waterford.org
Subject: Re: pg_dumpall
In-Reply-To: <3CE18C64.B2EEB710@waterford.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox