| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | <fabriziomello(at)gmail(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Marko Tiikkaja <marko(at)joh(dot)to>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Change pg_cancel_*() to ignore current backend |
| Date: | 2015-05-20 05:40:08 |
| Message-ID: | 555C1E38.9020905@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| Attachment | Content-Type | Size |
|---|---|---|
| pg__backend_skip_pid.patch | text/plain | 6.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Petr Jelinek | 2015-05-20 05:43:43 | Re: jsonb concatenate operator's semantics seem questionable |
| Previous Message | Chris Rogers | 2015-05-20 04:58:49 | Re: CTE optimization fence on the todo list? |