Re: Import Statistics in postgres_fdw before resorting to sampling.

Corey Huinker <corey.huinker@gmail.com>

From: Corey Huinker <corey.huinker@gmail.com>

To: Etsuro Fujita <etsuro.fujita@gmail.com>

Cc: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>, Michael Paquier <michael@paquier.xyz>, pgsql-hackers@postgresql.org, jkatz@postgresql.org, nathandbossart@gmail.com

Date: 2026-03-14T20:05:41Z

Lists: pgsql-hackers

Attachments

v15-0001-Add-FDW-functions-for-importing-optimizer-statis.patch (text/x-patch) patch v15-0001
v15-0002-Add-remote-statistics-fetching-to-postgres_fdw.patch (text/x-patch) patch v15-0002
v15-0003-Add-remote_analyze-to-postgres_fdw-remote-statis.patch (text/x-patch) patch v15-0003

>
>
> I've also moved the column matching - finding which rows of the attstats
> result set match to which columns in the local table - up into the fetch
> portion, something you had mentioned wanting to see as well. This resulted
> in some significant refactoring, but overall I think you will find the
> changes for the better.
>

I've added a reset of the result set indexes. Probably not necessary given
that we only keep the result set if all the columns found homes, but good
for peace of mind.

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

postgres_fdw: Replace buffers in RemoteAttributeMapping with pointers.
- aa1f93a3387a 19 (unreleased) landed
Add support for importing statistics from remote servers.
- 28972b6fc3dc 19 (unreleased) landed