| From: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
|---|---|
| To: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, MauMau <maumau307(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Statement-level rollback |
| Date: | 2017-11-02 08:16:35 |
| Message-ID: | CAB=Je-FPr7+pYX_08S7seQNtVN9w8UXE-FOQdN6OZ+0vTmb0oA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
Tsunakawa>So the statement-level rollback is newer to users, isn't it?
Technically speaking, the feature was listed in the changelog.
Tsunakawa>Doesn't PgJDBC execute RELEASE after each SQL statement?
It does not.
Tsunakawa>That said, even with RELEASE, the server memory bloat is not
solved.
That is what I mean.
Vladimir
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2017-11-02 08:22:51 | Re: [POC] hash partitioning |
| Previous Message | amul sul | 2017-11-02 08:15:22 | Re: [POC] hash partitioning |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2017-11-02 08:44:44 | Re: Statement-level rollback |
| Previous Message | Tsunakawa, Takayuki | 2017-11-02 06:16:44 | Re: Statement-level rollback |