| From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
|---|---|
| To: | legrand legrand <legrand_legrand(at)hotmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Statement-level rollback |
| Date: | 2017-03-07 22:19:57 |
| Message-ID: | CADK3HHJ0NHXn_PJuR10GohuT1rSycDJxHoXmJXJyfy7SEpWjAA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
You have to turn it on using the autosave parameter. it's not on by
default, and apparently not documented
Dave Cramer
davec(at)postgresintl(dot)com
www.postgresintl.com
On 7 March 2017 at 17:15, legrand legrand <legrand_legrand(at)hotmail(dot)com>
wrote:
> 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: RE: Statement-level rollback
> <http://www.postgresql-archive.org/Statement-level-rollback-tp5946725p5948053.html>
>
> Sent from the PostgreSQL - hackers mailing list archive
> <http://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html> at
> Nabble.com.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vladimir Sitnikov | 2017-03-07 22:26:49 | Re: Statement-level rollback |
| Previous Message | legrand legrand | 2017-03-07 22:15:32 | Re: Statement-level rollback |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vladimir Sitnikov | 2017-03-07 22:26:49 | Re: Statement-level rollback |
| Previous Message | legrand legrand | 2017-03-07 22:15:32 | Re: Statement-level rollback |