aboutsummaryrefslogtreecommitdiff
path: root/doc/src/sgml/ref/commit.sgml
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2024-05-18 14:26:05 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2024-05-18 14:26:13 -0400
commit779ac2c74bd15744aa92b588f70606a1a95256d2 (patch)
tree57d669805d0f7e7347e114f9b8feae5cb61f9e28 /doc/src/sgml/ref/commit.sgml
parent3f49df98d8b97adc37f408ef3942a1523fd33649 (diff)
downloadpostgresql-779ac2c74bd15744aa92b588f70606a1a95256d2.tar.gz
postgresql-779ac2c74bd15744aa92b588f70606a1a95256d2.zip
Add test case showing that commit d0d44049d fixed a live bug.
When I committed d0d44049d (Account for optimized MinMax aggregates during SS_finalize_plan), I didn't have a test case showing that it was fixing any reachable bug. Here is one, based on bug #18465 from Hal Takahara. Without the fix, all rows of the result show the same "min" value, because the aggregate doesn't get recalculated. Committed despite beta1 release freeze, with the concurrence of pgsql-release. Discussion: https://postgr.es/m/18465-2fae927718976b22@postgresql.org Discussion: https://postgr.es/m/2391880.1689025003@sss.pgh.pa.us
Diffstat (limited to 'doc/src/sgml/ref/commit.sgml')
0 files changed, 0 insertions, 0 deletions