On Thu, Aug 31, 2023 at 12:17 PM Corey Huinker <corey.huin...@gmail.com> wrote: > > While the primary purpose of the import function(s) are to reduce downtime > during an upgrade, it is not hard to see that they could also be used to > facilitate tuning and development operations, asking questions like "how might > this query plan change if this table has 1000x rows in it?", without actually > putting those rows into the table.
Thanks. I think this may be used with postgres_fdw to import statistics directly from the foreigns server, whenever possible, rather than fetching the rows and building it locally. If it's known that the stats on foreign and local servers match for a foreign table, we will be one step closer to accurately estimating the cost of a foreign plan locally rather than through EXPLAIN. -- Best Wishes, Ashutosh Bapat
