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-18T01:56:54Z
Lists: pgsql-hackers

Attachments

On Sat, Mar 14, 2026 at 4:05 PM Corey Huinker <corey.huinker@gmail.com>
wrote:

>
>> 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.
>

And rebased to make the CI happy.

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. postgres_fdw: Replace buffers in RemoteAttributeMapping with pointers.

  2. Add support for importing statistics from remote servers.