Re: use of SPI by postgresImportForeignStatistics

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
Cc: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: use of SPI by postgresImportForeignStatistics
Date: 2026-06-16 22:57:04
Message-ID: CA+TgmobLcuO+6gSLftG8gQFBZx1DyVt88JZ4--292FQJkKDs4A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 16, 2026 at 6:50 PM Corey Huinker <corey(dot)huinker(at)gmail(dot)com> wrote:
> postgres_fdw will get slimmer for not having SPI in it. relation_stats.c and attribute_stats.c will have some temporary bloat until things can be refactored.

Whatever ends up in core can (indeed must) be reused by every FDW. So
making things simpler for the FDW and more complex for core seems
likely to be the right tradeoff in general.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-06-16 23:02:13 Re: Direction for test frameworks: Perl TAP vs. Python/pytest
Previous Message Enrique Sánchez 2026-06-16 22:51:05 Re: Show estimated number of groups for IncrementalSort in EXPLAIN