diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2018-03-25 16:15:15 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2018-03-25 16:15:15 -0400 |
| commit | c515ff8d0a979fb553136a71388017c97785acda (patch) | |
| tree | c257616e81bbe1f4eff295d011e6e832c8970987 /src/backend/executor/nodeModifyTable.c | |
| parent | d0c0c894533f906b13b79813f02b2982ac675074 (diff) | |
| download | postgresql-c515ff8d0a979fb553136a71388017c97785acda.tar.gz postgresql-c515ff8d0a979fb553136a71388017c97785acda.zip | |
Doc: add example of type resolution in nested UNIONs.
Section 10.5 didn't say explicitly that multiple UNIONs are resolved
pairwise. Since the resolution algorithm is described as taking any
number of inputs, readers might well think that a query like
"select x union select y union select z" would be resolved by
considering x, y, and z in one resolution step. But that's not what
happens (and I think that behavior is per SQL spec). Add an example
clarifying this point.
Per bug #15129 from Philippe Beaudoin.
Discussion: https://postgr.es/m/152196085023.32649.9916472370480121694@wrigleys.postgresql.org
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions