Resent-From: POSTGRES mailing list <postman@postgres.Berkeley.EDU>
Resent-Message-Id: <199604021512.HAA22066@nobozo.CS.Berkeley.EDU>
Sender: owner-postman@postgres.Berkeley.EDU
Date: Tue, 2 Apr 1996 07:12:41 -0800
Message-Id: <199604021512.HAA22009@nobozo.CS.Berkeley.EDU>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: mariposa_hackers@postgres.Berkeley.EDU
From: Jeff Sidell <jsidell@cs.berkeley.edu>
Subject: B-tree bug
Cc: postgres@postgres.Berkeley.EDU
Resent-To: postgres-redist@postgres.Berkeley.EDU
Resent-Date: Tue, 02 Apr 96 07:12:50 -0800
Resent-XMts: smtp

When a b-tree index's scan position is marked, only the
line pointer value is saved.  If the position is restored
after the index scan has read past that page, it doesn't
work.  I noticed this while doing a merge-join with index
scans beneath it (tpc-D query #8).  I have reproduced the
bug with much smaller datasets.  The code to be changed is
in backend/executor/nodeIndexScan.  The procedures are
ExecIndexMarkPos() and ExecIndexRestrPos().

Has anyone else found this bug and possibly fixed it?

Jeff
=============================================================================
                                  JEFF SIDELL

Computer Science Division                            jsidell@cs.berkeley.edu
University of California at Berkeley    http://http.cs.berkeley.edu/~jsidell/
=============================================================================


==============================================================================
   To add/remove yourself to/from the POSTGRES mailing list: send mail with 
   the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU".
   If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
   a human will deal with it.  DO NOT post to the "postgres" mailing list.
==============================================================================
              URL: http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/