Re: How to know killed by pg_terminate_backend
От | Robert Haas |
---|---|
Тема | Re: How to know killed by pg_terminate_backend |
Дата | |
Msg-id | AANLkTil5fOjAV14F68OV78d5VOrzawMvTkIrlgsiwUy5@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: How to know killed by pg_terminate_backend (Tatsuo Ishii <ishii@postgresql.org>) |
Ответы |
Re: How to know killed by pg_terminate_backend
|
Список | pgsql-hackers |
On Thu, May 13, 2010 at 8:20 PM, Tatsuo Ishii <ishii@postgresql.org> wrote: >> > Maybe we could make PostgreSQL a little bit smarter so that it returns >> > a different code than 57P01 when killed by pg_terminate_backend(). >> >> Seems reasonable. Does the victim backend currently know why it has been >> killed? > > I don't think so. > > One idea is postmaster sets a flag in the shared memory area > indicating it rceived SIGTERM before forwarding the signal to > backends. > > Backend check the flag and if it's not set, it knows that the signal > has been sent by pg_terminate_backend(), not postmaster. Or it could also be sent by some other user process, like the user running "kill" from the shell. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company
В списке pgsql-hackers по дате отправления: