[PATCH] Minor patch to correct symbol name in logs
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:t37444psql -h localhost -U postgresBuilt from patchset v1 (message #1), July 27, 2026 at 10:16 PM.
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 t37444_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 t37444_1 && git checkout t37444_1Patchset v1 (message #1) is on t37444_1
Hi,
Backend's lo_functions were renamed to avoid conflicting with libpq
prototypes in commit - 6fc547960dbe0b8bd6cefae5ab7ec3605a5c46fc.
Logs inside those functions still refer to old symbol names, Here is the
small patch to update the same.
Thanks & Regards,
Vaishnavi,
Fujitsu Australia.
On 9/20/17 01:56, Vaishnavi Prabakaran wrote:
Backend's lo_functions were renamed to avoid conflicting with libpq
prototypes in commit - 6fc547960dbe0b8bd6cefae5ab7ec3605a5c46fc.Logs inside those functions still refer to old symbol names, Here is the
small patch to update the same.
I think those debug messages refer to the SQL name of the function, so
they look correct to me as is.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers