| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: O(n) tasks cause lengthy startups and checkpoints |
| Date: | 2021-12-01 22:56:32 |
| Message-ID: | 20211201225632.wrbrrofm4cbxvnqw@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2021-12-01 20:24:25 +0000, Bossart, Nathan wrote:
> I realize adding a new maintenance worker might be a bit heavy-handed,
> but I think it would be nice to have somewhere to offload tasks that
> really shouldn't impact startup and checkpointing. I imagine such a
> process would come in handy down the road, too. WDYT?
-1. I think the overhead of an additional worker is disproportional here. And
there's simplicity benefits in having a predictable cleanup interlock as well.
I think particularly for the snapshot stuff it'd be better to optimize away
unnecessary snapshot files, rather than making the cleanup more asynchronous.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Nancarrow | 2021-12-01 23:21:39 | Re: Data is copied twice when specifying both child and parent table in publication |
| Previous Message | Andres Freund | 2021-12-01 22:52:43 | Re: pg_replslotdata - a tool for displaying replication slot information |