]> git.ipfire.org Git - thirdparty/postgresql.git/commit
projects / thirdparty / postgresql.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 75b6104) | patch
Copy sub-Query nodes to avoid trouble when same sub-Query is linked to
authorTom Lane <tgl@sss.pgh.pa.us>
Sun, 6 Aug 2000 04:13:22 +0000 (04:13 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Sun, 6 Aug 2000 04:13:22 +0000 (04:13 +0000)
commit465a3b0a2494091450da12975fece1613fdcc68a
treeb79de77c50b5d3ba06cfbe7ec0a209145db01a70tree | snapshot
parent75b61043b0e95b2ff1f8b9d82c8ecf6a23519b3ccommit | diff
Copy sub-Query nodes to avoid trouble when same sub-Query is linked to
multiple times in the parsetree (can happen in COALESCE or BETWEEN
contexts, for example).  This is a pretty grotty solution --- it will
do for now, but perhaps we can do better when we redesign querytrees.
What we need is a consistent policy about whether querytrees should be
considered read-only structures or not ...
src/backend/optimizer/plan/subselect.c diff | blob | blame | history
Mirror of https://git.postgresql.org/git/postgresql.git