From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Mark Mielke" <mark(at)mark(dot)mielke(dot)cc>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: INSERT ... SELECT ... FOR SHARED? |
Date: | 2008-04-21 12:48:46 |
Message-ID: | 87od838jbl.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> 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=# begin;
BEGIN
postgres=# select * from tellers for share;
tid | bid | tbalance | filler
-----+-----+----------+--------
1 | 1 | 0 |
2 | 1 | 0 |
3 | 1 | 0 |
4 | 1 | 0 |
5 | 1 | 0 |
6 | 1 | 0 |
7 | 1 | 0 |
8 | 1 | 0 |
9 | 1 | 0 |
10 | 1 | 0 |
(10 rows)
postgres=# select distinct age(xmax) from tellers;
age
-----
0
(1 row)
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2008-04-21 13:12:29 | Re: TODO, FAQs to Wiki? |
Previous Message | Pavan Deolasee | 2008-04-21 12:40:48 | Re: Regression test fails when BLCKSZ is 1kB |