Re: advisory locks and permissions - Mailing list pgsql-hackers

From Tom Lane
Subject Re: advisory locks and permissions
Date
Msg-id 9517.1158951960@sss.pgh.pa.us
Whole thread Raw
In response to Re: advisory locks and permissions  ("Jim C. Nasby" <jim@nasby.net>)
List pgsql-hackers
"Jim C. Nasby" <jim@nasby.net> writes:
> Ahh, ok, I didn't realize that the total lock space was larger than
> what's being exposed today. That means we can easily add that stuff in
> the future and not break anything, which is all I was looking for.

Yeah --- in particular, we can always add more LOCKTAG values, or make
use of field4 values that are not possible with the current API.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: advisory locks and permissions
Next
From: Stephen Frost
Date:
Subject: Re: advisory locks and permissions