strict-aliasing warning
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:t139042psql -h localhost -U postgresBuilt from patchset v1 (message #1), September 20, 2026 at 09:21 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 t139042_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 t139042_1 && git checkout t139042_1Patchset v1 (message #1) is on t139042_1
On 12/9/25 18:27, ma lz wrote:
What version of Postgres?
In function "ExecEvalJsonCoercionFinish()"
if (SOFT_ERROR_OCCURRED(&jsestate->escontext))
may produce strict-aliasing warning
Don't use IsA may fix this problem
Why is it a problem?
This is something that should be submitted here(you will need create a
community account):
https://www.postgresql.org/account/login/?next=/account/submitbug/
--
Adrian Klaver
adrian.klaver@aklaver.com
On Tue, Dec 09, 2025 at 07:04:23PM -0800, Adrian Klaver wrote:
On 12/9/25 18:27, ma lz wrote:
Don't use IsA may fix this problem
Why is it a problem?
Well, I don't think that this has proved to be a problem until now in
the buildfarm. I doubt that it would be the only problematic area if
a new compiler flag is enforced by a buildfarm member, assuming that
we would add one but the bar is very high when it comes to that.
A 4-line message is short to present your arguments, what you are
trying to do, and why it could make sense in some way.
--
Michael