problem inserting in GIN index

Alvaro Herrera <alvherre@commandprompt.com> writes:

A guy just reported on pgsql-es-ayuda that he's getting
ERROR: item pointer (543108,2) already exists

Test case?

regards, tom lane

Tom Lane wrote:

Alvaro Herrera <alvherre@commandprompt.com> writes:

A guy just reported on pgsql-es-ayuda that he's getting
ERROR: item pointer (543108,2) already exists

Test case?

Apparently there's a crash involved ...

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

2009/3/9 Alvaro Herrera <alvherre@commandprompt.com>:

Tom Lane wrote:

Alvaro Herrera <alvherre@commandprompt.com> writes:

A guy just reported on pgsql-es-ayuda that he's getting
ERROR: item pointer (543108,2) already exists

Test case?

Apparently there's a crash involved ...

I asked to Gabriel. The exactly version is 8.3.6.
He just deleted the indexes :(

--
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

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

--
Emanuel Calvo Franco
Sumate al ARPUG !
(www.postgres-arg.org -
www.arpug.com.ar)
ArPUG / AOSUG Member
Postgresql Support & Admin

A guy just reported on pgsql-es-ayuda that he's getting

ERROR: item pointer (543108,2) already exists

It will be fine to get test case...

Apparently this message only occurs on GIN, in insertItemPointer

Reading that routine I cannot help but wonder -- where is
gdi->btree.curitem incremented?

At dataPlaceToPage and dataSplitPage called by ginInsertValue().

--
Teodor Sigaev E-mail: teodor@sigaev.ru
WWW: http://www.sigaev.ru/

Apparently there's a crash involved ...

Are other indexes on that table broken? ( Just count(*) with only index scan
enabled )
--
Teodor Sigaev E-mail: teodor@sigaev.ru
WWW: http://www.sigaev.ru/

2009/3/10 Teodor Sigaev <teodor@sigaev.ru>:

Apparently there's a crash involved ...

Are other indexes on that table broken? ( Just count(*) with only index scan
enabled )
--
Teodor Sigaev                                   E-mail: teodor@sigaev.ru
                                                  WWW: http://www.sigaev.ru/

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

Yes, there are some btree indexes broken.
Alvaro asked him if the option fsync is off.

--
Emanuel Calvo Franco
Sumate al ARPUG !
(www.postgres-arg.org -
www.arpug.com.ar)
ArPUG / AOSUG Member
Postgresql Support & Admin

Emanuel Calvo Franco escribi�:

2009/3/10 Teodor Sigaev <teodor@sigaev.ru>:

Apparently there's a crash involved ...

Are other indexes on that table broken? ( Just count(*) with only index scan
enabled )

Yes, there are some btree indexes broken.
Alvaro asked him if the option fsync is off.

We don't know whether the btree indexes are on the same table, though :-)

Since he already erased all the evidence, I don't think there's anything
to do about this for now.

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support