| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Alexander Kukushkin <cyberdemn(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Subject: | Re: Autovacuum worker doesn't immediately exit on postmaster death |
| Date: | 2020-10-29 16:35:07 |
| Message-ID: | 20201029163507.GA20933@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-Oct-28, Alexander Kukushkin wrote:
> Hello,
>
> I know, nobody in their mind should do that, but, if the postmaster
> process is killed with SIGKILL signal, most backend processes
> correctly notice the fact of the postmaster process absence and exit.
> There is one exception though, when there are autovacuum worker
> processes they are continuing to run until eventually finish and exit.
So, if you have a manual vacuum running on the table (with
vacuum_cost_delay=0) and kill -KILL the postmaster, that one also
lingers arbitrarily long afterwards?
(I suppose the problem is not as obvious just because the vacuum
wouldn't run as long, because of no vacuum cost delay; but it'd still be
a problem if you made the table bigger.)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2020-10-29 17:00:20 | Re: pg_dump, ATTACH, and independently restorable child partitions |
| Previous Message | Alvaro Herrera | 2020-10-29 16:32:27 | Re: Autovacuum worker doesn't immediately exit on postmaster death |