Possible bug in new VACUUM code

Hi,
   I  just stumbled over a very hard to reproduce error. Running   a "VACUUM ANALYZE <table>" concurrently to a
database heavy   under  load  caused a SELECT ... FOR UPDATE with full primary   key qualification to return multiple
resultsfrom that table.   The  table  contains  only  a few rows which receive ton's of   updates.
 
   System is 7.2B3 under Linux.
   Will try to produce a test case, just to let ppl know  early.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #



_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com