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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

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: Wed, 30 Apr 2008 23:28:37 +0000 (UTC)
  • Message-id: <20080430232837.26C7B7559CC@cvs.postgresql.org> <text/plain>

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)



Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group