| From: | Yan Chunlu <springrider(at)gmail(dot)com> |
|---|---|
| To: | Szymon Guz <mabewlun(at)gmail(dot)com> |
| Cc: | pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: how could duplicate pkey exist in psql? |
| Date: | 2011-11-17 11:18:24 |
| Message-ID: | CAOA66tHuMHDDDwKqN5eWiOOB3mVXudRg1ZJCZivftbNH8tv+Zw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)gmail(dot)com> wrote:
>
>
> On 17 November 2011 06:19, Yan Chunlu <springrider(at)gmail(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yan Chunlu | 2011-11-17 11:21:40 | Re: how could duplicate pkey exist in psql? |
| Previous Message | Craig Ringer | 2011-11-17 11:01:42 | Re: Is it ever necessary to vacuum a table that only gets inserts/updates? |