| From: | Jon Nelson <jnelson(at)jamponi(dot)net> | 
|---|---|
| To: | David Steele <david(at)pgmasters(dot)net> | 
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Marko Tiikkaja <marko(at)joh(dot)to>, fabriziomello(at)gmail(dot)com, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> | 
| Subject: | Re: Change pg_cancel_*() to ignore current backend | 
| Date: | 2015-05-20 12:38:35 | 
| Message-ID: | CAKuK5J12ynF2k4WsL7VBOHHwN-idUEohqYYZx=pwUZEkAQ0T9A@mail.gmail.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
On May 20, 2015 6:43 AM, "David Steele" <david(at)pgmasters(dot)net> wrote:
>
> On 5/20/15 1:40 AM, Jim Nasby wrote:
> > On 5/19/15 9:19 PM, Fabrízio de Royes Mello wrote:
> >>     We could add a second parameter to the current functions:
> >>     allow_own_pid DEFAULT false. To me that seems better than an
> >>     entirely separate set of functions.
> >>
> >>
> >> +1 to add a second parameter to current functions.
> >
> > Instead of allow_own_pid, I went with skip_own_pid. I have the function
> > still returning true even when it skips it's own PID... that seems a bit
> > weird, but I think it's better than returning false. Unless someone
> > thinks it should return NULL, but I don't see that as any better either.
>
> +1.  I agree that cancelling/killing your own process should not be the
> default behavior.
-1.  It breaks backwards compatibility. I use this function a fair bit to
terminate the current backend all the time.  Changing the signature is
great, by make the default behavior retain the current behavior.
>
> --
> - David Steele
> david(at)pgmasters(dot)net
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2015-05-20 13:06:41 | Re: Problems with question marks in operators (JDBC, ECPG, ...) | 
| Previous Message | David Steele | 2015-05-20 11:41:58 | Re: Change pg_cancel_*() to ignore current backend |