Re: Import Statistics in postgres_fdw before resorting to sampling.

From: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
To: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>
Cc: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers(at)postgresql(dot)org, jkatz(at)postgresql(dot)org, nathandbossart(at)gmail(dot)com
Subject: Re: Import Statistics in postgres_fdw before resorting to sampling.
Date: 2026-03-14 20:05:41
Message-ID: CADkLM=eozfsr-2hmuhBa71ATizWo7LQ01ZkJFbDqCKwC-f7ZHQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

Attachment Content-Type Size
v15-0001-Add-FDW-functions-for-importing-optimizer-statis.patch text/x-patch 5.0 KB
v15-0002-Add-remote-statistics-fetching-to-postgres_fdw.patch text/x-patch 37.3 KB
v15-0003-Add-remote_analyze-to-postgres_fdw-remote-statis.patch text/x-patch 13.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Lukas Fittl 2026-03-14 20:49:23 Re: Stack-based tracking of per-node WAL/buffer usage
Previous Message Corey Huinker 2026-03-14 19:51:29 Re: Import Statistics in postgres_fdw before resorting to sampling.