Re: Allow pg_dump --statistics-only to dump foreign table statistics?

From: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, pgsql(at)j-davis(dot)com
Subject: Re: Allow pg_dump --statistics-only to dump foreign table statistics?
Date: 2025-06-16 19:39:07
Message-ID: CADkLM=ezJjmiVM9NwP1w7f5aKg-KUUP0KGePNLf27qXwtsJzWw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> I skimmed through the main thread for the feature [0] (which seems to be so
> long that it sometimes doesn't load completely), and I didn't see anything
> directly related to the topic. There was some discussion about importing
> foreign relation stats with the new functions instead of remote table
> samples, but that's a different thing

If we aren't exporting stats for foreign tables then that is an oversight,
the intention always was to fetch all available statistics for all
relations. I can't offhand think of where we even have the option to
exclude them.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ranier Vilela 2025-06-16 19:44:05 Avoid possible dereference null pointer (src/backend/utils/cache/relcache.c)
Previous Message Corey Huinker 2025-06-16 19:35:48 Re: pg_dump --with-* options