| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Victor Yegorov <vyegorov(at)gmail(dot)com>, Alexander Kukushkin <cyberdemn(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Autovacuum worker doesn't immediately exit on postmaster death |
| Date: | 2020-10-29 21:36:31 |
| Message-ID: | 20201029213631.GA32022@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-Oct-29, Stephen Frost wrote:
> I do think it'd be good to find a way to check every once in a while
> even when we aren't going to delay though. Not sure what the best
> answer there is.
Maybe instead of thinking specifically in terms of vacuum, we could
count buffer accesses (read from kernel) and check the latch once every
1000th such, or something like that. Then a very long query doesn't
have to wait until it's run to completion. The cost is one integer
addition per syscall, which should be bearable.
(This doesn't help with a query that's running arbitrarily outside of
Postgres, or doing something that doesn't access disk -- but it'd help
with a majority of problem cases.)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2020-10-29 21:37:07 | -Wformat-signedness |
| Previous Message | Daniel Gustafsson | 2020-10-29 21:26:54 | Consistent error reporting for encryption/decryption in pgcrypto |