Message-ID: <1454331343.5847.98.camel@gmail.com>
Subject: Re: Insert in table with UNIQUE index
From: jaime soler <jaime.soler@gmail.com>
Reply-To: jaime.soler@gmail.com
To: Albe Laurenz <laurenz.albe@wien.gv.at>, 'Artem Tomyuk *EXTERN*'
 <admin@leboutique.com>, "pgsql-admin@postgresql.org"
 <pgsql-admin@postgresql.org>
Date: Mon, 01 Feb 2016 13:55:43 +0100
In-Reply-To: 
 <A737B7A37273E048B164557ADEF4A58B537D9AF2@ntex2010i.host.magwien.gv.at>
References: 
 <CANYYVqKwbPTj8JHS1MqYVnXzVtAr25bO+eEBWceCz2npoW0Vbg@mail.gmail.com>
 <A737B7A37273E048B164557ADEF4A58B537D9AF2@ntex2010i.host.magwien.gv.at>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

El mié, 27-01-2016 a las 14:12 +0000, Albe Laurenz escribió:
> Artem Tomyuk wrote:
> > I have a table with unique index with 2 exactly the same rows.
> > How it can be possible?
> > 
> > 
> > CREATE TABLE _inforgchngr6716_test
> > (
> >   _nodetref bytea NOT NULL,
> >   _noderref bytea NOT NULL,
> >   _messageno numeric(10,0)
> > )
> > WITH (
> >   OIDS=FALSE
> > );
> > ALTER TABLE _inforgchngr6716_test
> >   OWNER TO postgres;
> > 
> > -- Index: _inforg6716_bynodemsg_rn_test
> > 
> > -- DROP INDEX _inforg6716_bynodemsg_rn_test;
> > 
> > CREATE UNIQUE INDEX _inforg6716_bynodemsg_rn_test
> >   ON _inforgchngr6716_test
> >   USING btree
> >   (_nodetref, _noderref, _messageno);
> 
> Maybe index corruption.
> Did you have any crashes?

To discard a index corruption problem, try to select duplicates row
setting enable_indexscan and enable_bitmapscan to false and check if
you get 1 or 2 rows, if you get 2 -> I'll follow Albe advide and
reindex 
> 
> Do you get an error when you
>    REINDEX INDEX _inforg6716_bynodemsg_rn_test;
> 
> Yours,
> Laurenz Albe
> 


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