On Sat, Sep 26, 2026 at 1:28 AM Kirill Reshke <[email protected]> wrote: > Looks like I wrongly blamed 0ee83dd4a99 as root cause. > On 8e11859102f947e6145acdd809e5cdcdfbe90fa5 (eager aggregation), I got
> ANALYZE > ERROR: Aggref found where not expected FWIW, this is a duplicate of the bug reported by Robert (finding2 in [1]), and a proposed fix was provided there. [1] https://postgr.es/m/ca+tgmob7ism9ykrm44vjuduacchw-fy54mv5njptztl9uny...@mail.gmail.com - Richard
