Re: Change pg_cancel_*() to ignore current backend

From: Jon Nelson <jnelson+pgsql(at)jamponi(dot)net>
To:
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Change pg_cancel_*() to ignore current backend
Date: 2015-05-20 16:15:52
Message-ID: CAKuK5J2eodxtrysHqV=2ebFGTVCnpBT8jdxtTV2A_7AzGBBLLw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 20, 2015 at 9:09 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2015-05-20 16:18:38 Re: Problems with question marks in operators (JDBC, ECPG, ...)
Previous Message Robert Haas 2015-05-20 15:47:15 Re: Run pgindent now?