From: | John Smith <john_smith_45678(at)yahoo(dot)com> |
---|---|
To: | PG-General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: increment_by@ |
Date: | 2003-06-10 21:45:34 |
Message-ID: | 20030610214534.65145.qmail@web40703.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
This did the trick:
update pg_attribute set attname='increment_by' where
attname like 'increment_by(at)%';
Not sure what the problem with this was:
update pg_attribute set attname='increment_by' where
attrelid=457191;
ERROR: Cannot insert a duplicate key into unique
index pg_attribute_relid_attnam_index
John
--- Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> John Smith <john_smith_45678(at)yahoo(dot)com> writes:
> > This is a follow-up to my previous email. Using
> > phppgadmin to look at the sequence causing
> problems,
> > one of the columns is "increment_by@". How can
> I
> > change it back or otherwise fix it? What happened
> > anyhow?
>
> Sounds like a data corruption problem :-(. You
> might want to try a
> "select * from pg_attribute" and see if any other
> rows look obviously
> bogus.
>
> As for fixing it, you might be able to get away with
> an ALTER TABLE
> RENAME column --- I'm not sure if the system will
> let you apply that to
> a sequence or not, but it'd be worth trying.
> Failing that, a direct
> UPDATE on the messed-up row of pg_attribute ought to
> do the trick.
>
> Or you could just drop and recreate the affected
> sequence. There's not
> all that much state in a sequence ...
>
> regards, tom lane
__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Darko Prenosil | 2003-06-10 21:49:03 | Re: DBCS |
Previous Message | Forest Wilkinson | 2003-06-10 21:45:07 | How to enumerate foreign key constraints after migrating from 7.1.3? |