Remove unused param rte in set_plain_rel_pathlist
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:t46921psql -h localhost -U postgresBuilt from patchset v1 (message #1), September 20, 2026 at 05:32 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 t46921_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 t46921_1 && git checkout t46921_1Patchset v1 (message #1) is on t46921_1
Hi, hackers
Param RangeTblEntry *rte in function set_plain_rel_pathlist is not used at all.
I look at the commit e2fa76d80b(10 years ago), it’s useless since then.
Add a path to remove it.
Regards,
Zhang Mingli
Import Notes
Reply to msg id not found: e93595ee-e092-4a29-af42-e37aba15f9e8@SparkReference msg id not found: e93595ee-e092-4a29-af42-e37aba15f9e8@Spark
Zhang Mingli <zmlpostgres@gmail.com> writes:
Param RangeTblEntry *rte in function set_plain_rel_pathlist is not used at all.
Add a path to remove it.
I'm disinclined to change that, as it'd make set_plain_rel_pathlist
different from its sibling functions, which do need the RTE.
In practice this has cost zero anyway, since set_plain_rel_pathlist
will surely get inlined into its sole caller.
regards, tom lane