Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Function to kill backend

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Oliver Jowett <oliver(at)opencloud(dot)com>,Andreas Pflug <pgadmin(at)pse-consulting(dot)de>,Dave Page <dpage(at)vale-housing(dot)co(dot)uk>,Magnus Hagander <mha(at)sollentuna(dot)net>,Josh Berkus <josh(at)agliodbs(dot)com>,PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [HACKERS] Function to kill backend
Date: 2004-07-27 02:08:09
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
Tom Lane wrote:
> Oliver Jowett <oliver(at)opencloud(dot)com> writes:
> > Tom Lane wrote:
> >> So what you'd basically need is a separate signal to trigger that sort
> >> of exit, which would be easy ... if we had any spare signal numbers.
> > What about multiplexing it onto an existing signal? e.g. set a 
> > shared-mem flag saying "exit after cancel" then send SIGINT?
> Possible, but then the *only* way to get the behavior is by using the
> backend function --- you couldn't use dear old kill(1) to do it
> manually.  It'd be better if it mapped to a signal.

And what happens if a FATAL comes while it is procesing a signal meant
for termination?  It wouldn't exit fast enough --- bad.

  Bruce Momjian                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to

pgsql-patches by date

Next:From: Alvaro HerreraDate: 2004-07-27 02:41:53
Subject: [subxacts] Some docs
Previous:From: Peter EisentrautDate: 2004-07-26 22:16:42
Subject: Re: win32 version info

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group