On 15.03.2017 16:38, Robert Haas wrote:
On Wed, Mar 15, 2017 at 2:29 AM, Peter van Hardenberg wrote:
Ads and I were talking over breakfast about usability issues and he
mentioned transaction cancellation during interactive sessions as a serious
pain point.
I suggest we update the
Just chiming in: I rely heavily on the current default behavior
because it prevents large statements pasted into psql that cause
errors in transactions from partially running, and if it were changed
I would have caused production outages.
On Wed, Mar 15, 2017 at 8:42 AM, Pavel Stehule
2017-03-15 16:38 GMT+01:00 Robert Haas :
> On Wed, Mar 15, 2017 at 2:29 AM, Peter van Hardenberg wrote:
> > Ads and I were talking over breakfast about usability issues and he
> > mentioned transaction cancellation during interactive sessions as a
> serious
>
On Wed, Mar 15, 2017 at 2:29 AM, Peter van Hardenberg wrote:
> Ads and I were talking over breakfast about usability issues and he
> mentioned transaction cancellation during interactive sessions as a serious
> pain point.
>
> I suggest we update the default of ON_ERROR_ROLLBACK to
Peter van Hardenberg writes:
> It's quite clear to me that the current default behaviour costs the world
> serious pain and heart-ache on a daily basis.
This is a large claim for which you've provided little evidence. On the
other hand, changing behavior like this from one version
From: pgsql-hackers-ow...@postgresql.org
> [mailto:pgsql-hackers-ow...@postgresql.org] On Behalf Of Peter van
> Hardenberg
> I suggest we update the default of ON_ERROR_ROLLBACK to interactive for
> 10.0.
+1
Regards
Takayuki Tsunakawa
--
Sent via pgsql-hackers mailing list
All,
Ads and I were talking over breakfast about usability issues and he
mentioned transaction cancellation during interactive sessions as a serious
pain point.
I suggest we update the default of ON_ERROR_ROLLBACK to interactive for
10.0.
The last discussion I could find about this subject was