Re: how could duplicate pkey exist in psql? - Mailing list pgsql-general

From Yan Chunlu
Subject Re: how could duplicate pkey exist in psql?
Date
Msg-id CAOA66tHuMHDDDwKqN5eWiOOB3mVXudRg1ZJCZivftbNH8tv+Zw@mail.gmail.com
Whole thread Raw
In response to Re: how could duplicate pkey exist in psql?  (Szymon Guz <mabewlun@gmail.com>)
List pgsql-general
seems they are identical:
   159292 | |funnypicscn_link_karma|
   159292 | |funnypicscn_link_karma|

On Thu, Nov 17, 2011 at 4:07 PM, Szymon Guz <mabewlun@gmail.com> wrote:


On 17 November 2011 06:19, Yan Chunlu <springrider@gmail.com> wrote:
recently I have found several tables has exactly the same pkey,  here is the definition:
"diggcontent_data_account_pkey" PRIMARY KEY, btree (thing_id, key)


the data is like this:

   159292 | funnypics_link_point       | 41                                                                                                                     | num
   159292 | funnypics_link_point       | 40                                                                                                                     | num


I could not even update this record.

really confused about how could this happen... thanks!

Hi,
could you send us result of the query: 
select thing_id, '|'||key||'|' from table? 
Maybe there are some more spaces in the key column which were hidden by table alignment in the client?

regards
Szymon

pgsql-general by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Is it ever necessary to vacuum a table that only gets inserts/updates?
Next
From: Yan Chunlu
Date:
Subject: Re: how could duplicate pkey exist in psql?