Re: I incrementally altered my database into a state where backups couldn't be restored.

From: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
To: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
Cc: Adam Tomjack <adamtj(at)zuerchertech(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: I incrementally altered my database into a state where backups couldn't be restored.
Date: 2007-10-31 11:26:17
Message-ID: 47286659.4060406@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Heikki Linnakangas wrote:
> Adam Tomjack wrote:
>> I was able to put my database into a state where I couldn't restore a
>> backup without manually editing the backup file.
>
> I can't reproduce that on 8.1 or 8.2 or CVS HEAD. pg_dump produces this
> CREATE statement for the view:
>
> CREATE VIEW v_a_b_c AS
> SELECT b.aid, b.bid, c.cid FROM ((b JOIN c USING (bid)) JOIN a USING
> (aid));
>
> Not the CREATE OR REPLACE with a SELECT * you posted.

Greg Stark pointed out that the above doesn't work either, though it's
not the exact same output you posted.

I don't see any feasible way to fix that, unfortunately. We'd need to
rewrite view definition quite a bit behind the scenes.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2007-10-31 13:31:12 Re: I incrementally altered my database into a state where backups couldn't be restored.
Previous Message Gregory Stark 2007-10-31 10:56:09 Re: I incrementally altered my database into a state where backups couldn't be restored.