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

From Jon Nelson
Subject Re: Change pg_cancel_*() to ignore current backend
Date
Msg-id CAKuK5J2eodxtrysHqV=2ebFGTVCnpBT8jdxtTV2A_7AzGBBLLw@mail.gmail.com
Whole thread Raw
In response to Re: Change pg_cancel_*() to ignore current backend  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Change pg_cancel_*() to ignore current backend  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
On Wed, May 20, 2015 at 9:09 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> I think backwards compatibility probably trumps that argument.  I have
> no objection to providing a different call that behaves this way, but
> changing the behavior of existing applications will face a *much*
> higher barrier to acceptance.  Especially since a real use-case for
> the current behavior was shown upthread, which means you can't argue
> that it's simply a bug.
>
>                         regards, tom lane


Agree.
It breaks backwards compatibility. I use this function a fair bit to
terminate the current backend all the time.

-- 
Jon



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Run pgindent now?
Next
From: "David G. Johnston"
Date:
Subject: Re: Problems with question marks in operators (JDBC, ECPG, ...)