| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-jdbc(at)postgreSQL(dot)org |
| Subject: | Re: JDBC feature request: auto savepoint per command |
| Date: | 2007-04-24 18:26:33 |
| Message-ID: | Pine.BSO.4.64.0704231515230.22670@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Mon, 23 Apr 2007, Tom Lane wrote:
> Can anyone see a solution for this in the context of the existing driver
> facilities? If not, is it reasonable to ask for a driver option to do
> auto-savepointing? There is already an equivalent facility in psql, so
> the idea doesn't seem unreasonable to me.
>
Previous discussions on this topic had the idea that auto-savepointing
would be done on a per-connection basis enabled via a URL parameter or
DataSource option. In an application server would you have a separate
connection pool for auto-savepointing connections? Would you force all
transactions to use auto-savepoints even if they didn't want/need them?
You could enable/disable it dynamically, but that would require pg
specific code, is that what they want to do?
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-04-24 19:26:31 | Re: JDBC feature request: auto savepoint per command |
| Previous Message | Kris Jurka | 2007-04-24 18:22:28 | Re: Can't build postgresql-jdbc-8.2-505 on Fedora 7 |