| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Tyson Lloyd Thwaites <tyson(dot)lloydthwaites(at)allianza(dot)com(dot)au> |
| Cc: | Webb Sprague <webb(dot)sprague(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: [RESEND] Transaction auto-abort causes grief with Spring Framework |
| Date: | 2007-08-17 06:34:03 |
| Message-ID: | 20070817063403.GA20103@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Aug 17, 2007 at 03:18:30PM +0930, Tyson Lloyd Thwaites wrote:
> It seems like something that would be fairly easy to change... I don't
> know. I read someone talking about putting automatic checkpoints on
> every statement that goes through the jdbc driver to get around this
> issue. Perhaps this is the only way... unless pg could be put in a mode
> where it did this for you... like autocommit, but auto-checkpoint.
FWIW, this is exactly how the psql client handles "ON_ERROR continue".
There is resistance to building it into the protocol itself since the
autocommit fiasco. The backward compatability issues are daunting and
as pointed it can be handled adequately inside the driver
(jdbc/odbc/etc).
(That's not to say it couldn't be made easier for the clients also. For
example as part of the query request have a flag that says: start
savepoint prior to execution.)
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tyson Lloyd Thwaites | 2007-08-17 06:34:08 | Re: [RESEND] Transaction auto-abort causes grief with Spring Framework |
| Previous Message | Tyson Lloyd Thwaites | 2007-08-17 05:48:30 | Re: [RESEND] Transaction auto-abort causes grief with Spring Framework |