Jan Wieck writes:
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 results from that table.
Urgh. But I am not sure that you should be pointing the finger at
VACUUM. It doesn't move any tuples around (at least not in ctid
terms), so how could it possibly produce multiple tuple images in
another scan? My early bet is that the problem is not directly
related to VACUUM.

Post as soon as you have any more info ... remember there are lots
of eyeballs out here ...

regards, tom lane

Search Discussions

Discussion Posts

Previous

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 2 of 3 | next ›
Discussion Overview
grouppgsql-hackers @
categoriespostgresql
postedNov 28, '01 at 12:46a
activeNov 28, '01 at 12:00p
posts3
users3
websitepostgresql.org...
irc#postgresql

People

Translate

site design / logo © 2022 Grokbase