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-30T20:05:43Z
Lists: pgsql-hackers
>
> You forgot to pass the res to pgfdw_report_error for proper logging.
> I fixed this in the patch I posted just before.
>

+1


>
> > I've update the logic that we don't try to fetch attrstats if the
> reltuples is 0 or -1, and though the comments still mention the difference
> in server version, the code behaves the same in new versions and old. My
> thinking is that either value means "you are not going to find attstats"
> and our reaction is the same either way.
>

Agree.

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.