Re: How to know killed by pg_terminate_backend
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Itagaki Takahiro <itagaki.takahiro@gmail.com>
Cc: Tatsuo Ishii <ishii@postgresql.org>, pgsql-hackers@postgresql.org, robertmhaas@gmail.com, heikki.linnakangas@enterprisedb.com
Date: 2011-01-21T15:35:46Z
Lists: pgsql-hackers
Itagaki Takahiro <itagaki.takahiro@gmail.com> writes: > On Fri, Jan 21, 2011 at 13:56, Tatsuo Ishii <ishii@postgresql.org> wrote: >> Anyone has better idea? Tom dislikes my patch but I don't know how to >> deal with it. > There was another design in the past discussion: > One idea is postmaster sets a flag in the shared memory area > indicating it rceived SIGTERM before forwarding the signal to > backends. > Is it enough for your purpose and do we think it is more robust way? To put this as briefly as possible: I don't want to add even one line of code to distinguish pg_terminate_backend from database-wide shutdown. That function should be a last-ditch tool, not something used on a daily basis. So I disagree with the premise as much as with any particular implementation. regards, tom lane