Re: use of SEQ_MINVALUE in btree_gin - Mailing list pgsql-hackers

From Tom Lane
Subject Re: use of SEQ_MINVALUE in btree_gin
Date
Msg-id 25383.1468340798@sss.pgh.pa.us
Whole thread Raw
In response to use of SEQ_MINVALUE in btree_gin  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> btree_gin uses SEQ_MINVALUE as a way to get the smallest int64 value.
> This is actually wrong because the smallest int64 value is
> SEQ_MINVALUE-1, so this might be slightly broken.

> The whole thing was done as a convenience when INT64_IS_BUSTED had to be
> considered, but I think we can get rid of that now.  See attached
> proposed patch.

+1.  I agree that this is actually a bug fix, so it should be back-patched.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Showing parallel status in \df+
Next
From: Tom Lane
Date:
Subject: Re: GiST index build versus NaN coordinates