Re: Re: [HACKERS] New parameter RollbackError to control rollback behavior on error

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: "Inoue, Hiroshi" <inoue(at)tpf(dot)co(dot)jp>
Cc: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, PostgreSQL mailing lists <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: Re: [HACKERS] New parameter RollbackError to control rollback behavior on error
Date: 2014-03-28 05:37:30
Message-ID: CAB7nPqTbt0BDAWpjh7Gg+JOgYR4_D28KHXtfuaXVCS0Pty4+Ow@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-odbc

On Fri, Mar 28, 2014 at 12:53 PM, Inoue, Hiroshi <inoue(at)tpf(dot)co(dot)jp> wrote:
> (2014/03/27 20:55), Michael Paquier wrote:
>>
>> (Moving back this thread to pgsql-odbc, so keeping a maximum of message
>> history)
>
>
> As for the patch in the original post,
>
> Is there any difference between rollback_on_error and
> rollback_error_value except the naming?
No differences. I just changed the name of this variable to be a
maximum consistent with the parameter introduced.

> The length of connection strings seem to be increased at least 3 bytes.
> Is it right?
Do you mean that with the introduction of the new parameter AA? If
yes, well I guess it is increased by 5 bytes ";AA=[0|1|2]".
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2014-03-28 05:44:33 Re: History of WAL_LEVEL (archive vs hot_standby)
Previous Message Kyotaro HORIGUCHI 2014-03-28 05:06:59 Re: Archive recovery won't be completed on some situation.

Browse pgsql-odbc by date

  From Date Subject
Next Message Hiroshi Inoue 2014-03-28 22:16:35 Re: Re: [HACKERS] New parameter RollbackError to control rollback behavior on error
Previous Message Inoue, Hiroshi 2014-03-28 04:05:14 Re: Building odbc driver on windows