diff options
| author | Thomas Munro <tmunro@postgresql.org> | 2023-03-15 13:57:00 +1300 |
|---|---|---|
| committer | Thomas Munro <tmunro@postgresql.org> | 2023-03-15 14:02:49 +1300 |
| commit | d9c9c43af5c8d873f46a4b0c969a68deddd010b6 (patch) | |
| tree | 1276615f8f723d14422fe40a39789bb36c678541 /src/backend/executor | |
| parent | 06066915d48f072dcc5add048569ee7206772275 (diff) | |
| download | postgresql-d9c9c43af5c8d873f46a4b0c969a68deddd010b6.tar.gz postgresql-d9c9c43af5c8d873f46a4b0c969a68deddd010b6.zip | |
Fix fractional vacuum_cost_delay.
Commit 4753ef37 changed vacuum_delay_point() to use the WaitLatch() API,
to fix the problem that vacuum could keep running for a very long time
after the postmaster died.
Unfortunately, that broke commit caf626b2's support for fractional
vacuum_cost_delay, which shipped in PostgreSQL 12. WaitLatch() works in
whole milliseconds.
For now, revert the change from commit 4753ef37, but add an explicit
check for postmaster death. That's an extra system call on systems
other than Linux and FreeBSD, but that overhead doesn't matter much
considering that we willingly went to sleep and woke up again. (In
later work, we might add higher resolution timeouts to the latch API so
that we could do this with our standard programming pattern, but that
wouldn't be back-patched.)
Back-patch to 14, where commit 4753ef37 arrived.
Reported-by: Melanie Plageman <melanieplageman@gmail.com>
Discussion: https://postgr.es/m/CAAKRu_b-q0hXCBUCAATh0Z4Zi6UkiC0k2DFgoD3nC-r3SkR3tg%40mail.gmail.com
Diffstat (limited to 'src/backend/executor')
0 files changed, 0 insertions, 0 deletions