pgsql: Fix nodeTidscan.c to not trigger an error if the block number

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix nodeTidscan.c to not trigger an error if the block number
Date: 2008-04-30 23:28:37
Message-ID: 20080430232837.26C7B7559CC@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

Tags:
----
REL8_3_STABLE

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

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2008-05-01 19:55:40 pgsql: Make the minimum allowed value of work_mem be 64KB always, rather
Previous Message Tom Lane 2008-04-30 23:28:32 pgsql: Fix nodeTidscan.c to not trigger an error if the block number