"scott.marlowe" <[EMAIL PROTECTED]> writes:
> how odd. Since reindex works by dropping the index then recreating it, is
> it possible that some process inserted duplicates in the split second
> there was no index?
No, because reindex holds exclusive lock on the table for the whole
process.
AIL PROTECTED]>
To: "scott.marlowe" <[EMAIL PROTECTED]>
Cc: "Henrik Steffen" <[EMAIL PROTECTED]>; "Andrew Gould"
<[EMAIL PROTECTED]>; "pgsql" <[EMAIL PROTECTED]>
Sent: Tuesday, July 01, 2003 3:04 PM
Subject: Re: [GEN
Unlikely. Create index takes a write lock on a table. Reindex takes an
exclusive lock (or something like that). Unless something really bad happens
it shouldn't be a problem.
I've had index corruption before. We're running 7.0 (upgrading Real Soon
Now) and there are certain situations that can cor
>
> - Original Message -
> From: "Andrew Gould" <[EMAIL PROTECTED]>
> To: "Henrik Steffen" <[EMAIL PROTECTED]>
> Cc: "pgsql" <[EMAIL PROTECTED]>
> Sent: Monday, June 30, 2003 3:39 P
en" <[EMAIL PROTECTED]>
Cc: "pgsql" <[EMAIL PROTECTED]>
Sent: Monday, June 30, 2003 3:39 PM
Subject: Re: [GENERAL] Cannot create unique index
> Could you identify duplicated index values? Or were
> the messages erroneous?
>
> --- Henrik Steffen <[E
45563
- Original Message -
From: "Andrew Gould" <[EMAIL PROTECTED]>
To: "Henrik Steffen" <[EMAIL PROTECTED]>
Sent: Monday, June 30, 2003 2:46 PM
Subject: Re: [GENERAL] Cannot create unique index
> --- Henrik Steffen
Hello all,
REINDEXING a table I get the following message:
ERROR: Cannot create unique index. Table contains
non-unique values.
How can that be in REINDEXING ?
This means, that the index has been corrupted before,
because the index has always been unique. But somehow
the postmaster must have
