| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | How to know killed by pg_terminate_backend |
| Date: | 2010-05-13 00:24:52 |
| Message-ID: | 20100513.092452.96760179.t-ishii@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
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().
Comments?
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-05-13 00:48:41 | Stefan's bug (was: max_standby_delay considered harmful) |
| PostgreSQL : Re : | Brendan Hill | 2010-05-13 00:09:03 | Re: Query execution plan from 8.3 -> 8.4 |