| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | Michael Allman <msa(at)allman(dot)ms>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: jdbc xa support |
| Date: | 2005-07-23 23:28:06 |
| Message-ID: | 42E2D286.2060700@opencloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Allman | 2005-07-24 04:28:01 | Re: jdbc xa support |
| Previous Message | Heikki Linnakangas | 2005-07-23 21:12:49 | Re: jdbc xa support |