From: | aurora <aurora00(at)gmail(dot)com> |
---|---|
To: | "Jaime Casanova" <systemguards(at)gmail(dot)com> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Unexpected SQL error for UPDATE |
Date: | 2006-07-12 18:39:14 |
Message-ID: | cbd177510607121139l3f00b7cne1606f0854adc0ff@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Yes that helped!
reindex index users_email_address_text_key;
UPDATE users set email_address_text=email_address;
It kind of works now. Or at least it does not result in error. The UPDATE
query is running for more than an hour and still hasn't return. This is inline
with what we have seen before that coping 1 million fields seems to be
excessively slow.
About the index, it is created implicitly because of the UNIQUE constraint.
At this point right after the column is added, they are all null.
wy
On 7/12/06, Jaime Casanova <systemguards(at)gmail(dot)com> wrote:
>
> users_email_address_text_key sounds a lot like an index... is it an
> index? if so, what happenned if you REINDEX the table or even DROP and
> CREATE the index again? it certainly sounds to an index corruption.
>
> --
> regards,
> Jaime Casanova
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Aaron Bono | 2006-07-12 19:22:03 | Re: Can function results be used in WHERE? |
Previous Message | Scott Marlowe | 2006-07-12 18:13:18 | Re: How to find entries missing in 2nd table? |