diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2000-08-06 04:13:22 +0000 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2000-08-06 04:13:22 +0000 |
| commit | 465a3b0a2494091450da12975fece1613fdcc68a (patch) | |
| tree | b79de77c50b5d3ba06cfbe7ec0a209145db01a70 /src/backend/parser/parse_expr.c | |
| parent | 75b61043b0e95b2ff1f8b9d82c8ecf6a23519b3c (diff) | |
| download | postgresql-465a3b0a2494091450da12975fece1613fdcc68a.tar.gz postgresql-465a3b0a2494091450da12975fece1613fdcc68a.zip | |
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 ...
Diffstat (limited to 'src/backend/parser/parse_expr.c')
0 files changed, 0 insertions, 0 deletions