| From: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
|---|---|
| To: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Tomas Vondra <tomas(at)vondra(dot)me>, David Rowley <dgrowleyml(at)gmail(dot)com>, Kirill Reshke <reshkekirill(at)gmail(dot)com>, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Xuneng Zhou <xunengzhou(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Subject: | Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access) |
| Date: | 2026-09-14 16:02:30 |
| Message-ID: | CAAKRu_Yqxh2TPNgt8Exe+xO57GaDhDX8LksrfFuz_jwJPXkXUQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Sep 10, 2026 at 3:25 PM Melanie Plageman
<melanieplageman(at)gmail(dot)com> wrote:
>
> It also reported that since d96f87332b3 the FSM will be less up to
> date on the standby since COPY FREEZE criteria for updating the FSM is
> if (action == BLK_NEEDS_REDO && freespace < BLCKSZ / 5) and the old
> VM record replay code had no such freespace check. I'll post a patch
> to fix that tomorrow. The fix is pretty simple: just update the FSM if
> the heap multi insert record sets the VM.
I've also pushed a fix for this.
- Melanie
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bryan Green | 2026-09-14 16:26:30 | Re: Do not scan index in right table if condition for left join evaluates to false using columns in left table |
| Previous Message | Melanie Plageman | 2026-09-14 15:49:28 | Re: WAL_LOG CREATE DATABASE strategy broken for non-standard page layouts |