| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Erik Dobák <erik(dot)dobak(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate |
| Date: | 2025-07-15 18:00:21 |
| Message-ID: | 936089.1752602421@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> The observed behavior of the server seems like a bug no matter how
> well-coded or not the software trying to make the connecting is. The
> server should be able to close and disallow clients no matter what they are
> doing.
We will SIGKILL recalcitrant children during an "immediate" shutdown.
"Fast" shutdown is not defined to do that, and should not do so
because it'd imply having to do an unclean restart later.
I just tested logical replication both ways between current master and
v14 branch tip, and in either case the publishing server stops pretty
much instantaneously after "pg_ctl stop -m fast". So I don't see
anything broken about our code, and I remain of the opinion that Qlik
is probably at fault.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-07-15 18:13:53 | Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution |
| Previous Message | David G. Johnston | 2025-07-15 16:27:36 | Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate |