Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
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)

pgsql-committers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group