| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Subject: | Re: Should vacuum process config file reload more often |
| Date: | 2023-04-06 21:45:16 |
| Message-ID: | 5028847C-937A-4CC2-B127-AFF5F9FB79C5@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 6 Apr 2023, at 23:06, Melanie Plageman <melanieplageman(at)gmail(dot)com> wrote:
> Autovacuum workers, at the end of VacuumUpdateCosts(), check if cost
> limit or cost delay have been changed. If they have, they assert that
> they don't already hold the AutovacuumLock, take it in shared mode, and
> do the logging.
Another idea would be to copy the values to local temp variables while holding
the lock, and release the lock before calling elog() to avoid holding the lock
over potential IO.
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2023-04-06 21:57:58 | Re: Improve logging when using Huge Pages |
| Previous Message | Melanie Plageman | 2023-04-06 21:44:31 | Re: Option to not use ringbuffer in VACUUM, using it in failsafe mode |