pgsql: Fix CHECK_RELATION_BLOCK_RANGE macro, which was not merely

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix CHECK_RELATION_BLOCK_RANGE macro, which was not merely
Date: 2007-07-15 23:46:20
Message-ID: 20070715234620.7AC6F9FB2C4@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Fix CHECK_RELATION_BLOCK_RANGE macro, which was not merely producing
a warning but was outright wrong.

Modified Files:
--------------
pgsql/contrib/pageinspect:
btreefuncs.c (r1.2 -> r1.3)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pageinspect/btreefuncs.c.diff?r1=1.2&r2=1.3)
pgsql/contrib/pgstattuple:
pgstatindex.c (r1.5 -> r1.6)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgstattuple/pgstatindex.c.diff?r1=1.5&r2=1.6)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2007-07-15 23:47:13 pgsql: Fix CHECK_RELATION_BLOCK_RANGE macro, which was not merely
Previous Message Tom Lane 2007-07-15 23:30:19 pgsql: Fix a passel of signed vs unsigned char warnings.