Hi, here's a bug report.
Below is a reply to a message I posted on pgsql-admin. I'm quoting it to
demonstrate that others have also seen this bug. Below it is my original
message regarding the bug.
From: Paul Breen [mailto:pbreen(at)computerpark(dot)co(dot)uk]
Sent: Monday, November 27, 2000 11:16 PM
To: Rainer Mager
Subject: Re: [ADMIN] Postgres 7 pgdump problems
Rainer - sorry for the late reply, I haven't been at work for a few days!
Yeah, we've seen this happen before (on an old 6.3.2 database). At first
I just noticed the view wasn't working and re-ran our 'create view' script
against the database. This fixed the view but had a knock-on effect and
screwed up another view (actually the next view when listing tables etc.
in the database using '\d')! It wasn't until I did a table listing that I
noticed that Postgres was listing the view as a table and - as you did - I
dropped the view as a table, then rebuilt it from our 'create view' script
and everything was OK. Never did find out why though?!! As you say, it
does smell like a bug.
Paul M. Breen, Software Engineer - Computer Park Ltd.
Tel: (01536) 417155
On Tue, 21 Nov 2000, Rainer Mager wrote:
> Hi all,
> We've run into an odd problem here. We had a db that we upgraded to PG7
> without problems. We then dumped that db via pgdump and restored it to a
> different server. The odd part is that the restored database had at least
> one view from the original db that magically turned into a table (not a
> view) in the new db. This broke some of our code that accesses the db (I
> can't remember exactly why off hand) so I had to delete the table and
> recreate it as a view by hand.
> Has anyone else seen this? It smells like a bug to me.
pgsql-bugs by date
|Next:||From: Alan Turner||Date: 2000-11-28 09:11:10|
|Subject: [BUG] PostgreSQL 7.0.3 backend dumps core.|
|Previous:||From: pgsql-bugs||Date: 2000-11-27 21:54:08|
|Subject: Both cross-named & compound foreign key constaints fail|