pgsql: Fix nodeTidscan.c to not trigger an error if the block number - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Fix nodeTidscan.c to not trigger an error if the block number
Date
Msg-id 20080430232832.3E78C7559CC@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Fix nodeTidscan.c to not trigger an error if the block number portion of
a user-supplied TID is out of range for the relation.  This is needed to
preserve compatibility with our pre-8.3 behavior, and it is sensible anyway
since if the query were implemented by brute force rather than optimized
into a TidScan, the behavior for a non-existent TID would be zero rows out,
never an error.  Per gripe from Gurjeet Singh.

Modified Files:
--------------
    pgsql/src/backend/executor:
        nodeTidscan.c (r1.58 -> r1.59)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/nodeTidscan.c?r1=1.58&r2=1.59)

pgsql-committers by date:

Previous
From: alvherre@postgresql.org (Alvaro Herrera)
Date:
Subject: pgsql: Add example showing how to remove a password from a role.
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Fix nodeTidscan.c to not trigger an error if the block number