Sub-millisecond [autovacuum_]vacuum_cost_delay broken

From: Melanie Plageman <melanieplageman(at)gmail(dot)com>
To: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Sub-millisecond [autovacuum_]vacuum_cost_delay broken
Date: 2023-03-09 21:26:02
Message-ID: CAAKRu_b-q0hXCBUCAATh0Z4Zi6UkiC0k2DFgoD3nC-r3SkR3tg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

I think that 4753ef37e0ed undid the work caf626b2c did to support
sub-millisecond delays for vacuum and autovacuum.

After 4753ef37e0ed, vacuum_delay_point()'s local variable msec is a
double which, after being passed to WaitLatch() as timeout, which is a
long, ends up being 0, so we don't end up waiting AFAICT.

When I set [autovacuum_]vacuum_delay_point to 0.5, SHOW will report that
it is 500us, but WaitLatch() is still getting 0 as timeout.

- Melanie

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2023-03-09 21:40:36 Re: Sub-millisecond [autovacuum_]vacuum_cost_delay broken
Previous Message Robert Haas 2023-03-09 21:15:12 Re: allow_in_place_tablespaces vs. pg_basebackup