| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: chained transactions |
| Date: | 2018-04-06 02:53:26 |
| Message-ID: | 69f81fb7-b227-e9a8-f64c-446bc997cdf8@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4/5/18 04:35, Heikki Linnakangas wrote:
> With this patch, this stops working:
>
> set transaction_isolation='default';
But why is this supposed to work? This form is not documented anywhere.
You can use RESET or SET TO DEFAULT.
I suspect this is some artifact in the implementation that this patch is
proposing to get rid of.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2018-04-06 02:53:56 | Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS |
| Previous Message | Michael Paquier | 2018-04-06 02:49:57 | Re: [HACKERS] Optional message to user when terminating/cancelling backend |