mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-11-21 03:13:05 +08:00
74618e2b82
* Add option to build with OpenSSL out of the box. Fix thusly exposed bit rot. Although it compiles now, getting this to do something useful is left as an exercise. * Fix Kerberos options to defer checking for required libraries until all the other libraries are checked for. * Change default odbcinst.ini and krb5.srvtab path to PREFIX/etc. * Install work around for Autoconf's install-sh relative path anomaly. Get rid of old INSTL_*_OPTS variables, now that we don't need them anymore. * Use `gunzip -c' instead of g?zcat. Reportedly broke on AIX. * Look for only one of readline.h or readline/readline.h, not both. * Make check for PS_STRINGS cacheable. Don't test for the header files separately. * Disable fcntl(F_SETLK) test on Linux. * Substitute the standard GCC warnings set into CFLAGS in configure, don't add it on in Makefile.global. * Sweep through contrib tree to teach makefiles standard semantics. ... and in completely unrelated news: * Make postmaster.opts arbitrary options-aware. I still think we need to save the environment as well. |
||
|---|---|---|
| .. | ||
| Makefile | ||
| README.user_locks | ||
| user_locks.c | ||
| user_locks.h | ||
| user_locks.sql.in | ||
User locks, by Massimo Dal Zotto <dz@cs.unitn.it> Copyright (C) 1999, Massimo Dal Zotto <dz@cs.unitn.it> This software is distributed under the GNU General Public License either version 2, or (at your option) any later version. This loadable module, together with my user-lock.patch applied to the backend, provides support for user-level long-term cooperative locks. For example one can write: select some_fields, user_write_lock_oid(oid) from table where id='key'; Now if the returned user_write_lock_oid field is 1 you have acquired an user lock on the oid of the selected tuple and can now do some long operation on it, like let the data being edited by the user. If it is 0 it means that the lock has been already acquired by some other process and you should not use that item until the other has finished. Note that in this case the query returns 0 immediately without waiting on the lock. This is good if the lock is held for long time. After you have finished your work on that item you can do: update table set some_fields where id='key'; select user_write_unlock_oid(oid) from table where id='key'; You can also ignore the failure and go ahead but this could produce conflicts or inconsistent data in your application. User locks require a cooperative behavior between users. User locks don't interfere with the normal locks used by postgres for transaction processing. This could also be done by setting a flag in the record itself but in this case you have the overhead of the updates to the records and there could be some locks not released if the backend or the application crashes before resetting the lock flag. It could also be done with a begin/end block but in this case the entire table would be locked by postgres and it is not acceptable to do this for a long period because other transactions would block completely. The generic user locks use two values, group and id, to identify a lock, which correspond to ip_posid and ip_blkid of an ItemPointerData. Group is a 16 bit value while id is a 32 bit integer which could also be an oid. The oid user lock functions, which take only an oid as argument, use a group equal to 0. The meaning of group and id is defined by the application. The user lock code just takes two numbers and tells you if the corresponding entity has been succesfully locked. What this mean is up to you. My succestion is that you use the group to identify an area of your application and the id to identify an object in this area. Or you can just lock the oid of the tuples which are by definition unique. Note also that a process can acquire more than one lock on the same entity and it must release the lock the corresponding number of times. This can be done calling the unlock funtion until it returns 0.