Re: Statistics Import and Export

From: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Davis <pgsql(at)j-davis(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, jian he <jian(dot)universality(at)gmail(dot)com>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Stephen Frost <sfrost(at)snowman(dot)net>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, alvherre(at)alvh(dot)no-ip(dot)org
Subject: Re: Statistics Import and Export
Date: 2025-02-24 21:47:30
Message-ID: CADkLM=frR91qu91REpV2HHUkCRffBZBYqkaQpMUDk-r6pke79w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Feb 24, 2025 at 4:33 PM Andres Freund <andres(at)anarazel(dot)de> wrote:

> Hi,
>
> On February 24, 2025 10:30:08 PM GMT+01:00, Corey Huinker <
> corey(dot)huinker(at)gmail(dot)com> wrote:
> >From what I can see, it doesn't. Moreover, the attstattarget array agg is
> >only done in version 11 and higher, and we need to go as far back as we've
> >got expression indexes.
>
> I don't think we have to at all. It's perfectly reasonable to add a
> complicated feature like this only when upgrading from newer versions. I'd
> go even so far to say that it's a bad idea to support unsupported source
> versions, because it'll mean we'll practically get very very little testing
> for those paths but claim to support them.
>

Anyone still on those versions has some serious barriers to doing an
upgrade, downtime probably being the largest of them. Any stats we don't
migrate here have to be analyzed later, which is more downtime or time in a
degraded state. I'd rather we try to make it easier for them to upgrade,
and in this case the risk is small because we're just collecting the
attname:attnum pairings for an index, and it's the same SQL that we'd use
for modern versions.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2025-02-24 21:51:02 Re: Serverside SNI support in libpq
Previous Message James Hunter 2025-02-24 21:46:49 Re: Proposal: "query_work_mem" GUC, to distribute working memory to the query's individual operators