Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
Cc: jian he <jian(dot)universality(at)gmail(dot)com>, imchifan(at)163(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
Date: 2026-09-25 23:53:45
Message-ID: arcJiWiWBrkGn2Ig@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Sep 25, 2026 at 03:45:10PM -0400, Corey Huinker wrote:
> This is a good move, as it further opens the door to making stats import
> work with custom stakinds, but a lot of things need to happen [1][2][3]
> before we can even attempt that.

I don't know much about these parts, only about the problem at hand,
which is enough for me for the moment.. :)

> It does apply cleanly to 19, and yes, the v18 is a bigger change, and will
> look much more like my patch unless we decide to backport
> statatt_get_type()...which probably isn't worth it.

The backpatch of v18 is not that bad, isolated within
attribute_stats.c, so the ABI argument does not apply.
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Previous Message Manu 2026-09-25 22:03:24 Re: autovacuum: automatically propagate updated parameters