diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2005-04-29 22:28:24 +0000 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2005-04-29 22:28:24 +0000 |
commit | 3a694bb0a16fea1662f1ffd31506a72effdd4a93 (patch) | |
tree | 50bbf16b3117aada49b2709f524b3bdcf1a36815 /src/backend/utils/adt/arrayfuncs.c | |
parent | 32d3b47e6f05c7137debddb68730a25fe1bb0cd6 (diff) | |
download | postgresql-3a694bb0a16fea1662f1ffd31506a72effdd4a93.tar.gz postgresql-3a694bb0a16fea1662f1ffd31506a72effdd4a93.zip |
Restructure LOCKTAG as per discussions of a couple months ago.
Essentially, we shoehorn in a lockable-object-type field by taking
a byte away from the lockmethodid, which can surely fit in one byte
instead of two. This allows less artificial definitions of all the
other fields of LOCKTAG; we can get rid of the special pg_xactlock
pseudo-relation, and also support locks on individual tuples and
general database objects (including shared objects). None of those
possibilities are actually exploited just yet, however.
I removed pg_xactlock from pg_class, but did not force initdb for
that change. At this point, relkind 's' (SPECIAL) is unused and
could be removed entirely.
Diffstat (limited to 'src/backend/utils/adt/arrayfuncs.c')
0 files changed, 0 insertions, 0 deletions