From: aurora <aurora00@gmail.com>
To: Jaime Casanova <systemguards@gmail.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Unexpected SQL error for UPDATE
Date: Wed, 12 Jul 2006 11:39:14 -0700
Message-ID: <cbd177510607121139l3f00b7cne1606f0854adc0ff@mail.gmail.com> (raw)
In-Reply-To: <c2d9e70e0607120612g56d97f3cqd0a569a1784fd878@mail.gmail.com>
References: <cbd177510607111747h7542382bke12a6fc152338fe6@mail.gmail.com>
<c2d9e70e0607120612g56d97f3cqd0a569a1784fd878@mail.gmail.com>
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@gmail.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
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: aurora00@gmail.com, systemguards@gmail.com
Subject: Re: Unexpected SQL error for UPDATE
In-Reply-To: <cbd177510607121139l3f00b7cne1606f0854adc0ff@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox