| From: | legrand legrand <legrand_legrand(at)hotmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Statement-level rollback |
| Date: | 2017-03-07 22:15:32 |
| Message-ID: | DB5PR03MB102905210D7ABAA35B9BC612902F0@DB5PR03MB1029.eurprd03.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
Thanks !
that's a very good new !
I'm still receiving the famous
"current transaction is aborted" error
when usingversion 42.0.0 with
jdbc:postgresql://localhost:5432/postgres?autosave=always
But I will see that with pgjdbc team ;o)
Regards
PAscal
--
View this message in context: http://www.postgresql-archive.org/Statement-level-rollback-tp5946725p5948053.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2017-03-07 22:19:57 | Re: Statement-level rollback |
| Previous Message | Eric Ridge | 2017-03-07 22:10:41 | Example Custom Scan Provider Implementation? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2017-03-07 22:19:57 | Re: Statement-level rollback |
| Previous Message | Dave Cramer | 2017-03-07 21:38:19 | Re: Statement-level rollback |