| From: | Szymon Guz <mabewlun(at)gmail(dot)com> |
|---|---|
| To: | Yan Chunlu <springrider(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 08:07:07 |
| Message-ID: | CAFjNrYtn=SjFhBGwvM0WM_Z4=jJBuzV6fTRB=aktHA7z3RjYbA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 | Jason Buberel | 2011-11-17 09:05:01 | Re: Is it ever necessary to vacuum a table that only gets inserts/updates? |
| Previous Message | Albe Laurenz | 2011-11-17 08:03:44 | Re: how could duplicate pkey exist in psql? |