Gregory Stark <[EMAIL PROTECTED]> writes:
> "Tom Lane" <[EMAIL PROTECTED]> writes:
>> The lack of regression tests covering this area is a bit annoying
>> at this point. However, it's hard to see how to test FOR UPDATE
>> until we get some concurrent-sessions support in psql.
> Well, end-to-end testing would e better but we can test that the locks are
> at least being recorded by white-box inspection:
> postgres=# select distinct age(xmax) from tellers;
Huh, that's a cute trick ... and it would answer the immediate problem,
which is to check that the statement did take the row locks it was
supposed to.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
