Heikki Linnakangas wrote:
>> On a related note, can we get the backend to indicate if a transaction
>> was read-only when the "PREPARE TRANSACTION" statement is called?
>> (Also, I believe preparing a read-only transaction should
>> automatically "commit" it.) We could then return XA_RDONLY from the
>> driver's prepare() method in that case. As it is, it either throws an
>> exception or returns XA_OK.
>
>
> It should be possible, but we're already past the feature freeze so
> it'll have to wait for version 8.2. The backend already keeps track
> which transactions are read-only, and skips updating the clog for them.
> That information just needs to be exposed.
If the client uses Connection.setReadOnly() presumably we can track that
in the driver, which will catch some of the cases at least.
-O
