From: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
---|---|
To: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Lock compatibility matrix |
Date: | 2007-01-31 21:47:37 |
Message-ID: | Pine.LNX.4.64.0702010032510.400@sn.sai.msu.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi there,
following discussion in -patches about lock compatibility matrix,
posted by Teodor, we have another matrix
http://mira.sai.msu.su/~megera/pgsql/lockmatrix/c2.html
Besides formatting improvements, it has addtional lock with
temporary name UPDATE EXCLUSIVE (UE), which is the same as
EXCLUSIVE, but doesn't conflicts with SHARE UPDATE EXCLUSIVE (SUE),
which aquired by VACUUM and autovacuum. The reason for this is that
at present we have no lock mode, which doesn't conflicts with *vacuum.
The problem was described in thread
http://archives.postgresql.org/pgsql-general/2006-12/msg01476.php
What is the reason why we don't have such lock ?
Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru)
Sternberg Astronomical Institute, Moscow University, Russia
Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2007-01-31 22:00:02 | Re: "May", "can", "might" |
Previous Message | Tom Lane | 2007-01-31 20:41:31 | Re: [GENERAL] 8.2.1 Compiling Error |