pgsql: Do not use in-place updates for statistics import.

From: Jeff Davis <jdavis(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Do not use in-place updates for statistics import.
Date: 2025-02-25 01:12:26
Message-ID: E1tmjUo-000XVD-1J@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Do not use in-place updates for statistics import.

The use of in-place updates was originally there to follow the
precedent of ANALYZE and to reduce the potential for bloat on
pg_class. Per discussion, it's not worth the risks.

Reported-by: Andres Freund <andres(at)anarazel(dot)de>
Discussion: https://postgr.es/m/cpdanvzykcb5o64rmapkx6n5gjypoce3y52hff7ocxupgpbxu4@53jmlyvukijo

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/f3dae2ae5856dec9935a51e53216400566ef8d4f

Modified Files
--------------
src/backend/statistics/relation_stats.c | 138 ++++++++++-------------------
src/test/regress/expected/stats_import.out | 53 -----------
src/test/regress/sql/stats_import.sql | 33 -------
3 files changed, 47 insertions(+), 177 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Jeff Davis 2025-02-25 01:28:26 pgsql: Missing doc update for f3dae2ae58.
Previous Message Michael Paquier 2025-02-25 01:08:48 pgsql: psql: Add pipeline status to prompt and some state variables