| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: How to know killed by pg_terminate_backend |
| Date: | 2010-05-13 06:33:06 |
| Message-ID: | 4BEB9D22.6070503@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tatsuo Ishii wrote:
> If a backend killed by pg_terminate_backend(), the backend returns
> 57P01 which is identical to the one when it's killed by postmaster.
>
> Problem is, pgpool-II needs to trigger failover if postmaster goes
> down because apparently pgpool-II cannot use the PostgreSQL server
> anymore.
>
> On the otherhand, pg_terminate_backend() just terminates a backend. So
> triggering failover is overkill.
>
> 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?
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2010-05-13 06:49:13 | Re: multibyte charater set in levenshtein function |
| Previous Message | Devrim GÜNDÜZ | 2010-05-13 06:22:41 | Re: pg_upgrade code questions |