[PATCH] Check system cache invalidations before each command in transaction
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:t46737psql -h localhost -U postgresBuilt from patchset v1 (message #1), October 06, 2026 at 11:33 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 t46737_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 t46737_1 && git checkout t46737_1Patchset v1 (message #1) is on t46737_1
Hello guys.
In the previous discussion [1]/messages/by-id/1205251664297977@mail.yandex.ru we find out that while we are in
transaction function definition is not invalidated if it was redefined
in another session. Here is a patch to fix this. Also, I did a small
perfomance impact measurement (test.sh in attachment) on my home PC
with Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz. The result is (each
transaction is a 10 million calls to functions):
- without patch
latency average = 37087.639 ms
tps = 0.026963
- with patch
latency average = 38793.125 ms
tps = 0.025778
What do you think about it, guys?
[1]: /messages/by-id/1205251664297977@mail.yandex.ru
/messages/by-id/1205251664297977@mail.yandex.ru