Message-ID: <f588cdb7e5447af71110b2e9532b247c7efbd77c.camel@j-davis.com>
Subject: Re: Statistics Import and Export
From: Jeff Davis <pgsql@j-davis.com>
To: Andres Freund <andres@anarazel.de>, Corey Huinker
 <corey.huinker@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Michael Paquier <michael@paquier.xyz>, 
 jian he <jian.universality@gmail.com>, Nathan Bossart
 <nathandbossart@gmail.com>, Bruce Momjian <bruce@momjian.us>, Matthias van
 de Meent <boekewurm+postgres@gmail.com>,  Magnus Hagander
 <magnus@hagander.net>, Stephen Frost <sfrost@snowman.net>, Ashutosh Bapat
 <ashutosh.bapat.oss@gmail.com>, Peter Smith <smithpb2250@gmail.com>, 
 PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
 alvherre@alvh.no-ip.org
Date: Mon, 24 Feb 2025 12:41:21 -0800
In-Reply-To: <cpdanvzykcb5o64rmapkx6n5gjypoce3y52hff7ocxupgpbxu4@53jmlyvukijo>
References: 
	<blezfpeafycxlizyynwvwzh2vywmklhvfqudhicjrccu4raqpx@4ttfufowc2vo>
	 <3728741.1740178078@sss.pgh.pa.us>
	 <CADkLM=f0a43aTd88xW4xCFayEF25g-7hTrHX_WhV40HyocsUGg@mail.gmail.com>
	 <97b451228227c555be1a4f79c4a62ddec9a74f06.camel@j-davis.com>
	 <CADkLM=ckXu5wzSQZ3Y_fvAaL8rZ+upZdSecBLf5FCTMj7M6T-A@mail.gmail.com>
	 <b227c4fca29dfb893bb414ce6d84fc2377489ecc.camel@j-davis.com>
	 <CADkLM=dRMC6t8gp9GVf6y6E_r5EChQjMAAh_vPyih_zMiq0zvA@mail.gmail.com>
	 <y2d36zf6pl3n6ni6e4ctblu3a5iazi2dycknq53h2mjvp7lto4@hhww3h2qgdrw>
	 <1457469.1740419458@sss.pgh.pa.us>
	 <CADkLM=eWSv2z_DVB=psfwHitq7DbFJQaP9A46R27eARC-4OYtQ@mail.gmail.com>
	 <cpdanvzykcb5o64rmapkx6n5gjypoce3y52hff7ocxupgpbxu4@53jmlyvukijo>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.44.4-0ubuntu2 
MIME-Version: 1.0
Archived-At: <https://www.postgresql.org/message-id/f588cdb7e5447af71110b2e9532b247c7efbd77c.camel%40j-davis.com>
Precedence: bulk

On Mon, 2025-02-24 at 15:36 -0500, Andres Freund wrote:
> > 1. will inplace update pg_class to avoid table bloat
>=20
> I suspect that this is a *really* bad idea.

The reason we added it is that it's what ANALYZE does, and a big
restore bloats pg_class without it.

I don't think those are major concerns for v1, so in principle I'm fine
removing it. But the problem is that it affects the documented
semantics, so it would be hard to change later, and we'd be stuck with
the bloating behavior forever.

Regards,
	Jeff Davis