Re: estimation problems for DISTINCT ON with FDW
Jeff Janes <jeff.janes@gmail.com>
From: Jeff Janes <jeff.janes@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Etsuro Fujita <etsuro.fujita@gmail.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2020-07-25T17:30:22Z
Lists: pgsql-hackers
On Fri, Jul 3, 2020 at 5:50 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: > > OK, I'll go ahead and push the patch I proposed yesterday. > Thank you. I tested 12_STABLE with my real queries on the real data set, and the "hard coded" estimate of 200 distinct rows (when use_remote_estimte is turned back on) is enough to get rid of the worst plans I was seeing in 12.3. Cheers, Jeff
Commits
-
Clamp total-tuples estimates for foreign tables to ensure planner sanity.
- d83d59e42d0c 9.5.23 landed
- 69a3fe6e639a 9.6.19 landed
- 5144a40f3fa7 10.14 landed
- ef799bdd04ee 11.9 landed
- ca5e93f769e1 14.0 landed
- 9233624b128b 13.0 landed
- 153c14cdd714 12.4 landed