Multi delete wal IDEA
Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.
You can run a PostgreSQL built from this patch straight from Docker, with no checkout and no build:
docker run --rm -p 5432:5432 ghcr.io/hackorum-dev/postgres-patch:t50489psql -h localhost -U postgresBuilt from patchset v1 (message #1), August 17, 2026 at 09:37 AM.
Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:
git clone --branch t50489_1 https://github.com/hackorum-dev/postgres.gitIn a checkout you already have, add the fork once:
git remote add hackorum https://github.com/hackorum-dev/postgres.gitthen, for this patchset and every later one:
git fetch hackorum t50489_1 && git checkout t50489_1Patchset v1 (message #1) is on t50489_1
Hi there, hackers! How about trying out an idea to add an analog to save
memory in WAL files for deleting records, similar to multi-insert
optimization? This patch is trying to do just that.
Best Regards, Stepan Neretin!
On Thu, Oct 31, 2024 at 11:42 AM Stepan Neretin <sndcppg@gmail.com> wrote:
Hi there, hackers! How about trying out an idea to add an analog to save memory in WAL files for deleting records, similar to multi-insert optimization? This patch is trying to do just that.
Hi,
Thanks for the patch! Could you explain a bit more how this patch
works? I don't see changes in your patch to heap_delete() where WAL is
emitted, so I'm not sure I understand how it works. And could you
provide a small example or repro? It makes it much easier to review
and understand.
- Melanie