Re: Change pg_cancel_*() to ignore current backend - Mailing list pgsql-hackers

From Fabrízio de Royes Mello
Subject Re: Change pg_cancel_*() to ignore current backend
Date
Msg-id CAFcNs+pwRdBnG-Q3iXOFCoAV9EWJQBUam_x=XNMQTo9Mb1GA6Q@mail.gmail.com
Whole thread
In response to Re: Change pg_cancel_*() to ignore current backend  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
On Fri, May 22, 2015 at 3:28 PM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
>
> You and Andreas think it's fine as-is.
> Tom and Jon Nelson maybe don't like it as-is, but won't break backwards compatibility.
> David Steele and I seem fine with breaking compat., not sure about Fabrizio.
>

+1 to add a second parameter and -1 to break backward compatibility with the "default = true".

Regards,

--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog: http://fabriziomello.github.io
>> Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
>> Github: http://github.com/fabriziomello

pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: Change pg_cancel_*() to ignore current backend
Next
From: Jim Nasby
Date:
Subject: Re: jsonb concatenate operator's semantics seem questionable