aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2024-05-20 15:08:30 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2024-05-20 15:08:30 -0400
commit7204f35919b7e021e8d1bc9f2d76fd6bfcdd2070 (patch)
treed9a6ed2112d569e2c6b52eb60773c8524b37f1b2 /doc/src
parentd2a04470aa6401c1938cc107e0b2c56c22a2321f (diff)
downloadpostgresql-7204f35919b7e021e8d1bc9f2d76fd6bfcdd2070.tar.gz
postgresql-7204f35919b7e021e8d1bc9f2d76fd6bfcdd2070.zip
Revert commit 66c0185a3 and follow-on patches.
This reverts 66c0185a3 (Allow planner to use Merge Append to efficiently implement UNION) as well as the follow-on commits d5d2205c8, 3b1a7eb28, 7487044d6. In addition to those, 07746a8ef had to be removed then re-applied in a different place, because 66c0185a3 moved the relevant code. The reason for this last-minute thrashing is that depesz found a case in which the patched code creates a completely wrong plan that silently gives incorrect query results. It's unclear what the cause is or how many cases are affected, but with beta1 wrap staring us in the face, there's no time for closer investigation. After we figure that out, we can decide whether to un-revert this for beta2 or hold it for v18. Discussion: https://postgr.es/m/Zktzf926vslR35Fv@depesz.com (also some private discussion among pgsql-release)
Diffstat (limited to 'doc/src')
0 files changed, 0 insertions, 0 deletions