Re: [HACKERS] ON_ERROR_ROLLBACK

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bernd Helmle <mailings(at)oopsware(dot)de>
Cc: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] ON_ERROR_ROLLBACK
Date: 2014-12-30 14:20:06
Message-ID: 16128.1419949206@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Bernd Helmle <mailings(at)oopsware(dot)de> writes:
> --On 29. Dezember 2014 12:55:11 -0500 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Given the lack of previous complaints, this probably isn't backpatching
>> material, but it sure seems like a bit of attention to consistency
>> would be warranted here.

> Now that i read it i remember a client complaining about this some time
> ago. I forgot about it, but i think there's value in it to backpatch.

Hm. Last night I wrote the attached draft patch, which I was intending
to apply to HEAD only. The argument against back-patching is basically
that this might change the interpretation of scripts that had been
accepted silently before. For example
\set ECHO_HIDDEN NoExec
will now select "noexec" mode whereas before you silently got "on" mode.
In one light this is certainly a bug fix, but in another it's just
definitional instability.

If we'd gotten a field bug report we might well have chosen to back-patch,
though, and perhaps your client's complaint counts as that.

Opinions anyone?

regards, tom lane

Attachment Content-Type Size
psql-keyword-matching-cleanup.patch text/x-diff 23.2 KB

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Kevin Grittner 2014-12-30 15:14:13 Re: vacuum vs pg_repack vs pg_reorg
Previous Message Andy Colson 2014-12-30 14:12:02 Re: Improving performance of merging data between tables

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2014-12-30 14:38:12 Re: Additional role attributes && superuser review
Previous Message Heikki Linnakangas 2014-12-30 14:05:50 Re: What exactly is our CRC algorithm?