Re: Primary Key Problems

On Fri, 7 Dec 2001, Phill Kenoyer wrote:

> I took your advice and checked the string size using char_length() and
> octet_length(). They are the same.
>
> octet_length | stock | octet_length | inventory_type | client_id
> 5 | 10725 | 4 | used | 60
> 5 | 10725 | 4 | used | 60
>
> I do a daily pg_dump of the database and the scheme I posted was from
> that. So the primary key is still active.
>
> I just dont understand how I can have dups in the primary keys, unless
> it is a bug.

Hmm, what does explain show for your query? I'd wonder if the unique
index got corrupted for some reason and so didn't see the first value
when the second was inserted. If you search for a specific value
and try to force an index scan (use set enable_seqscan=false) do you
still get two rows (and does explain in that case show it using the
index?)