From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: functions.c: copy trees from source_list before parse analysis e |
Date: | 2025-04-04 22:26:58 |
Message-ID: | E1u0pV4-002hiL-0V@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
functions.c: copy trees from source_list before parse analysis etc.
This is yet another bit of fallout from the fact that backend/parser
(like other code) feels free to scribble on the parse tree it's
handed. In this case that resulted in modifying the
relatively-short-lived copy in the cached function's source_list.
That would be fine since we only need each source_list tree once
... except that if the parser fails after making some changes,
the function cache entry remains as-is and will still be there
if the user tries to execute the function again. Then we have
problems because we're feeding a non-pristine tree to the parser.
The most expedient fix is a quick copyObject(). I considered
other answers like somehow marking the cache entry invalid
temporarily, but that would add complexity and I'm not sure
it's worth it. In typical scenarios we'd only do this once
per function query per session.
Reported-by: Alexander Lakhin <exclusion(at)gmail(dot)com>
Author: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Discussion: https://postgr.es/m/6d442183-102c-498a-81d1-eeeb086cdc5a@gmail.com
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/0f43083d16f4be7c01efa80d05d0eef5e5ff69d3
Modified Files
--------------
src/backend/executor/functions.c | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2025-04-05 00:11:59 | pgsql: Repair misbehavior with duplicate entries in FK SET column lists |
Previous Message | Álvaro Herrera | 2025-04-04 21:40:48 | Re: pgsql: Prevent redeclaration of typedef TocEntry. |