From: | Myra Chachkin <myra(at)ack(dot)Berkeley(dot)EDU> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | Myra Chachkin <myra(at)ack(dot)Berkeley(dot)EDU>, sfpug(at)postgresql(dot)org |
Subject: | Re: drop table bug and how to recover? |
Date: | 2004-09-08 17:10:44 |
Message-ID: | 20040908101044.G16403@ack.Berkeley.EDU |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | sfpug |
Hi Josh et al,
On Wed, Sep 08, 2004 at 10:00:12AM -0700, Josh Berkus wrote:
> > We're running postgres 7.4.1.
>
> Well, first you should upgrade as soon as you can; 7.4.1 has a number of bugs
> related to database recovery you don't want to live with. Please note that
> there are some extra steps required for upgrade 7.4.1-->7.4.5.
I know...but thank you for the reminder.
> > I think I may have hit a drop table
> > bug? I created a table, then dropped it, but now get "relation
> > already exists" when I try to recreate it. There wasn't anything
> > weird about the table AFAIK, except that the rowid was defined with
> > a default nextval of another table's sequence (hence my drop). I
> > did this directly in the SQL monitor.
>
> Mind cutting and pasting the whole session? This is an unlikely bug as you
> have reported it, and it is more likely that something else is going on.
Unfortunately I don't have it any more, it was a few days ago. Is there
anything else I can do to troubleshoot?
Myra
From | Date | Subject | |
---|---|---|---|
Next Message | Myra Chachkin | 2004-09-08 17:14:20 | Re: drop table bug and how to recover? |
Previous Message | elein | 2004-09-08 17:03:11 | Re: drop table bug and how to recover? |