Postgres Pro
Downloads
Home   >   mailing lists

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

From Yan Chunlu
Subject how could duplicate pkey exist in psql?
Date
Msg-id CAOA66tE8TqJkQjCra+kNrr8YBS=wXkimN-jtAfNReuX2RAnt_A@mail.gmail.com
Whole thread Raw
Responses Re: how could duplicate pkey exist in psql?  ("Albe Laurenz" <laurenz.albe@wien.gv.at>)
Re: how could duplicate pkey exist in psql?  (Szymon Guz <mabewlun@gmail.com>)
Re: how could duplicate pkey exist in psql?  (Edson Richter <richter@simkorp.com.br>)
Re: how could duplicate pkey exist in psql?  (hubert depesz lubaczewski <depesz@depesz.com>)
List pgsql-general
Tree view
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!

pgsql-general by date:

Previous
From: John R Pierce
Date:
Subject: Re: Is it ever necessary to vacuum a table that only gets inserts/updates?
Next
From: Tom Lane
Date:
Subject: Re: Is it ever necessary to vacuum a table that only gets inserts/updates?