Neil Conway <nconway@klamath.dyndns.org> writes:
> AFAIK, current Postgres behavior when processing SELECT queries is like
> this:
> (1) for each tuple in the result set, try to get an
> AccessShareLock on it
Uh, no. There are no per-tuple locks, other than SELECT FOR UPDATE
which doesn't affect SELECT at all. AccessShareLock is taken on the
entire table, mainly as a means of ensuring the table doesn't disappear
from under us.
regards, tom lane
