pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rex Mabry <rexmabry@yahoo.com>
To: pgsql-admin@postgresql.org
Cc: subamathy <subamathy@gmail.com>
Subject: Re: Duplicate records in a table inspite of a primary key
Date: Tue, 12 Aug 2008 07:31:44 -0700 (PDT)
Message-ID: <462594.24414.qm@web35907.mail.mud.yahoo.com> (raw)
In-Reply-To: <200808121027.53405.xzilla@users.sourceforge.net>

You have to be careful when using characters as your PK.  A trailing space could give the appearance of duplicate keys.
Example:
"user1"
"user1 " (This one has a space at the end)

--- On Tue, 8/12/08, Robert Treat <xzilla@users.sourceforge.net> wrote:

From: Robert Treat <xzilla@users.sourceforge.net>
Subject: Re: [ADMIN] Duplicate records in a table inspite of a primary key
To: pgsql-admin@postgresql.org
Cc: "subamathy" <subamathy@gmail.com>
Date: Tuesday, August 12, 2008, 9:27 AM

On Tuesday 12 August 2008 02:47:58 subamathy wrote:
>  Hi,
>  We are having problems resulting from users being able to create
duplicate
> records
> in table.
>
>   Below is the description of the table
>  Column | Type | Modifiers
> -----------------------+------------------------+-----------
> user_id | character varying(128) | not null
> person_email_required | numeric(5,0) |
> wddx_data | text |
> proxy_id | character varying(128) |
> email_to | character varying(6) |
> password | character varying(60) |
> user_name | character varying(64) |
> language_preference | character varying(20) |
> enable_autosearch | character varying(6) |
> country_id | character varying(16) |
> Indexes:
> "i_personalise" PRIMARY KEY, btree (user_id)
> "i_personalise_proxy_id" btree (proxy_id)
> "i_personalise_user_id" btree (user_id)
>
>
> database version: PostgreSQL 8.0.1
>
> i_personalise- index
>
> conn type: Primary (constriant Type)
> condeferrable: False
> conkey: 1 (column which has constraint)
>
> Could you please help me out in finding the reason for such dupicate
> records existing
>
>
> Could you pls help me out in finding the reson for duplicate records being
> inserted.

I'm pretty sure that between 8.0.1 and 8.0.17 there are a couple of
bugfixes 
related to duplicate rows with pk scenarios, you should probably take some 
time to upgrade before you spend too much time digging into this (make sure 
to read all of the release notes for those versions in between, i'm also 
thinking there are some special instructions that might need to be done 
somewhere in there)

-- 
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL

-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



      

view thread (5+ messages)

Message-ID: <462594.24414.qm@web35907.mail.mud.yahoo.com>
Permalink:  ../462594.24414.qm@web35907.mail.mud.yahoo.com/
Also on:    postgresql.org/message-id/462594.24414.qm@web35907.mail.mud.yahoo.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: rexmabry@yahoo.com, subamathy@gmail.com
  Subject: Re: Duplicate records in a table inspite of a primary key
  In-Reply-To: <462594.24414.qm@web35907.mail.mud.yahoo.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox