Re: Evaluate arguments of correlated SubPlans in the referencing ExprState
Alena Rybakina <lena.ribackina@yandex.ru>
From: Alena Rybakina <lena.ribackina@yandex.ru>
To: vignesh C <vignesh21@gmail.com>
Cc: Andres Freund <andres@anarazel.de>,
Peter Eisentraut <peter@eisentraut.org>, pgsql-hackers@postgresql.org,
Tom Lane <tgl@sss.pgh.pa.us>
Date: 2024-01-28T09:07:46Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Evaluate arguments of correlated SubPlans in the referencing ExprState
- a7f107df2b70 18.0 landed
-
Doc: improve documentation for jsonpath behavior.
- 7014c9a4bba2 17.0 cited
Attachments
- v3-0001-WIP-Evaluate-arguments-of-correlated-SubPlans-in-the.patch (text/x-patch) patch v3-0001
On 26.01.2024 05:37, vignesh C wrote: > On Tue, 24 Oct 2023 at 01:47, Alena Rybakina <lena.ribackina@yandex.ru> wrote: >> Hi! >> >> I looked through your patch and noticed that it was not applied to the current version of the master. I rebased it and attached a version. I didn't see any problems and, honestly, no big changes were needed, all regression tests were passed. >> >> I think it's better to add a test, but to be honest, I haven't been able to come up with something yet. > The patch does not apply anymore as in CFBot at [1]: > > === Applying patches on top of PostgreSQL commit ID > 7014c9a4bba2d1b67d60687afb5b2091c1d07f73 === > === applying patch > ./v2-0001-WIP-Evaluate-arguments-of-correlated-SubPlans-in-the.patch > .... > patching file src/include/executor/execExpr.h > Hunk #1 succeeded at 160 (offset 1 line). > Hunk #2 succeeded at 382 (offset 2 lines). > Hunk #3 FAILED at 778. > 1 out of 3 hunks FAILED -- saving rejects to file > src/include/executor/execExpr.h.rej > patching file src/include/nodes/execnodes.h > Hunk #1 succeeded at 959 (offset 7 lines). > > Please have a look and post an updated version. > > [1] - http://cfbot.cputube.org/patch_46_4209.log > > Regards, > Vignesh Thank you! I fixed it. The code remains the same. -- Regards, Alena Rybakina Postgres Professional: http://www.postgrespro.com The Russian Postgres Company