use of SEQ_MINVALUE in btree_gin - Mailing list pgsql-hackers

From Peter Eisentraut
Subject use of SEQ_MINVALUE in btree_gin
Date
Msg-id 9ec6dce7-fbdd-98d7-85f8-0c18183b82c9@2ndquadrant.com
Whole thread Raw
Responses Re: use of SEQ_MINVALUE in btree_gin  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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.

--
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: remove checkpoint_warning
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: asynchronous and vectorized execution