Satoshi Nagayasu <[EMAIL PROTECTED]> writes:
> I think the read-only has two meanings for the user.
> First is the internal state. XID, OID or something like that.
> In these cases, the internal state mustn't be changed.
> Some users will need the read-only for internal state.
> Second is read-only for the user data contents.
> In some cases, the user want to make the user data as read-only.
> For this purpose, the user doesn't care XID or OID, I guess.
> So, we can implement them in different way.
> I think both are necessary.
Indeed, but we already have a implementation of the second form, in
a reasonably spec-compliant fashion. The TODO item concerns the first
form, which is something that the current system cannot do at all.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
