[PATCH] Remove dead code in pgcrypto
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.
This thread has been committed, so CI has stopped here. Anything below is the last result it produced.
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:t253398psql -h localhost -U postgresBuilt from patchset v1 (message #1), August 13, 2026 at 10:35 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 t253398_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 t253398_1 && git checkout t253398_1Patchset v1 (message #1) is on t253398_1
Hi,
I noticed that PGP_Context.mdc_checked field is write-only and not
used for anything. Since it's marked as an internal variable I'm
pretty confident it's safe to remove it. The patch is attached.
--
Best regards,
Aleksander Alekseev
On 13 Aug 2026, at 12:24, Aleksander Alekseev <aleksander@tigerdata.com> wrote:
I noticed that PGP_Context.mdc_checked field is write-only and not
used for anything. Since it's marked as an internal variable I'm
pretty confident it's safe to remove it. The patch is attached.
Agreed, will remove.
--
Daniel Gustafsson