| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | postgres(at)jeltef(dot)nl |
| Cc: | jacob(dot)champion(at)enterprisedb(dot)com, tomas(at)vondra(dot)me, zsolt(dot)parragi(at)percona(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org, davecramer(at)gmail(dot)com, hlinnaka(at)iki(dot)fi |
| Subject: | Re: Add GoAway protocol message for graceful but fast server shutdown/switchover |
| Date: | 2026-03-31 09:40:19 |
| Message-ID: | 20260331.184019.1086246580212079929.ishii@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I guess, I was not clear. Because the same problem exists for
> Pgpool-II. When pgpool forwards the message to the client, the client
> will disconnect from pgpool. But if connection_life_time is not
> reached (and by default this is unlimited) pgpool will not disconnect
> from the postgres server. So the postgres server has not actually
> achieved the intended goal, but the client still disconnected for no
> benefit, only downsides.
Right. However, in many installations of Pgpool-II, health check is
enabled. The health check process tries to connect to the PostgreSQL
server which is in shutdown sequence, and fails because it will get
"FATAL: the database system is shutting down" error. This will trigger
a failover of PgpoolII and the pooled connections to backend are gone
because all child process that holds the pools are killed, at least in
some cases.
Regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2026-03-31 09:55:37 | Re: SQL Property Graph Queries (SQL/PGQ) |
| Previous Message | Amit Kapila | 2026-03-31 09:36:00 | Re: Initial COPY of Logical Replication is too slow |