From 53927281c58e875d38834557e0d806baf4a771ab Mon Sep 17 00:00:00 2001 From: Corey Huinker Date: Mon, 3 Aug 2026 17:47:41 -0400 Subject: [PATCH v3 15/15] Doc: explain extended stats functions. The workflow for extended statistics is different enough from the workflows for relation and attribute statistics, and as a result the function patterns are different. --- src/backend/statistics/extended_stats_funcs.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/src/backend/statistics/extended_stats_funcs.c b/src/backend/statistics/extended_stats_funcs.c index 6db48022a63..236c8b98416 100644 --- a/src/backend/statistics/extended_stats_funcs.c +++ b/src/backend/statistics/extended_stats_funcs.c @@ -313,9 +313,11 @@ upsert_pg_statistic_ext_data(const Datum *values, const bool *nulls, * be updated. * * Unlike its attribute and relation equivalent functions, there is no - * corresponding extended_statistics_update_internal() function. This is mostly - * because there is not yet an internal update use-case where the statitics - * object is already locked. + * corresponding import_extended_statistics() function, and therefore there + * is only one entry point for extended_statistics_update(). As a result, + * there isn't yet the same value in separating out the locking and oid + * resolution from the statistics-value forming, so the current separation + * of duties remains. */ static bool extended_statistics_update(const NullableDatum *args) -- 2.50.1 (Apple Git-155)