MIME-Version: 1.0
References: 
 <CAA5RZ0tiL01rYm7=WaDGLUYjvz+fQRqmaXyRUv9jKRnR3_6xDQ@mail.gmail.com>
 <CADkLM=fn=RmBD0-h+yjTxhpLtbK9s_QdvT-HsGtUj+-1N=6s0g@mail.gmail.com>
 <CAA5RZ0sf7vYav+Q5GwxGikBZSYUm+4haA5bHC0N67ct570HLcg@mail.gmail.com>
 <abRugSlNTmW0-9Um@nathan>
 <CADkLM=cfpFMpgOGPEyr7U+-Cxzvukap-_s8p-ijMTyRphP=oeg@mail.gmail.com>
 <abhXqx-xffsknv3B@nathan>
 <CADkLM=cuwGZU0i51vn+SUqptXB8QT8rhRRYshns+pX0KxczmAQ@mail.gmail.com>
 <abhk0oLSA7lQ62jJ@nathan> <abh63Ro7XBvik6MD@paquier.xyz>
 <abiJtpb6FsluRpGk@nathan>
 <abiMCYxA5JI5T57P@paquier.xyz>
In-Reply-To: <abiMCYxA5JI5T57P@paquier.xyz>
From: Corey Huinker <corey.huinker@gmail.com>
Date: Mon, 16 Mar 2026 22:05:51 -0400
Message-ID: 
 <CADkLM=dc1P231z9X1-PgFsu6P+Bft4K9eE+nT7=zeX=_7YBuXQ@mail.gmail.com>
Subject: Re: Add starelid, attnum to pg_stats and leverage this in pg_dump
To: Michael Paquier <michael@paquier.xyz>
Cc: Nathan Bossart <nathandbossart@gmail.com>,
 Sami Imseih <samimseih@gmail.com>,
	pgsql-hackers@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000055016064d2ec770"
Archived-At: 
 <https://www.postgresql.org/message-id/CADkLM%3Ddc1P231z9X1-PgFsu6P%2BBft4K9eE%2BnT7%3DzeX%3D_7YBuXQ%40mail.gmail.com>
Precedence: bulk

--000000000000055016064d2ec770
Content-Type: text/plain; charset="UTF-8"

>
> Makes sense here to keep it simple.  I don't want to change the
> extstat restore code more than necessary at this stage of the CF
> calendar cycle, except for bugs and issues discussed during the beta
> cycle.


+1. I've also not advocated any changes to the extstat dump/restore code,
and I doubt I would until we start needing to fetch them in batches.

--000000000000055016064d2ec770
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote gmail_quote_container"><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex">Makes sense here to keep it simple=
.=C2=A0 I don&#39;t want to change the<br>
extstat restore code more than necessary at this stage of the CF<br>
calendar cycle, except for bugs and issues discussed during the beta<br>
cycle.</blockquote><div><br></div><div>+1.=C2=A0I&#39;ve also not advocated=
 any changes to the extstat dump/restore code, and I doubt I would until we=
 start needing to fetch them in batches.</div></div></div>

--000000000000055016064d2ec770--