From: tgl@postgresql.org
To: pgsql-committers@postgresql.org
Subject: pgsql: GIN's ItemPointerIsMin, ItemPointerIsMax, and
Date: Fri, 5 Jun 2009 18:50:53 +0000 (UTC)
Message-ID: <20090605185053.060D075331E@cvs.postgresql.org> (raw)
Log Message:
-----------
GIN's ItemPointerIsMin, ItemPointerIsMax, and ItemPointerIsLossyPage macros
should use GinItemPointerGetBlockNumber/GinItemPointerGetOffsetNumber,
not ItemPointerGetBlockNumber/ItemPointerGetOffsetNumber, because the latter
will Assert() on ip_posid == 0, ie a "Min" pointer. (Thus, ItemPointerIsMin
has never worked at all, but it seems unused at present.) I'm not certain
that the case can occur in normal functioning, but it's blowing up on me
while investigating Tatsuo-san's data corruption problem. In any case it
seems like a problem waiting to bite someone.
Back-patch just in case this really is a problem for somebody in the field.
Tags:
----
REL8_3_STABLE
Modified Files:
--------------
pgsql/src/include/access:
gin.h (r1.16.2.2 -> r1.16.2.3)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/access/gin.h?r1=1.16.2.2&r2=1.16.2.3)
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-committers@postgresql.org
Cc: tgl@postgresql.org
Subject: Re: pgsql: GIN's ItemPointerIsMin, ItemPointerIsMax, and
In-Reply-To: <20090605185053.060D075331E@cvs.postgresql.org>
* 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