Re: Statistics Import and Export

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, 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-21 22:20:48
Message-ID: 3725646.1740176448@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Corey Huinker <corey(dot)huinker(at)gmail(dot)com> writes:
>> I wonder whether we ought to issue different queries depending on
>> whether we're superuser. The pg_stats view is rather expensive
>> because of its security restrictions, and if we're superuser we
>> could just look directly at pg_statistic. Maybe those checks are
>> fast enough not to matter, but ...

> That could lead to a rather complicated query that has to replicate the
> guts of pg_stats for every server-specific version of pg_stats,
> specifically the CASE statements that transform
> the stakindN/stanumbersN/stavaluesN to mcv, correlation, etc, so I'd like
> to avoid that if possible.

Yeah, it'd be notationally ugly for sure. Let's keep that idea in the
back pocket and see how far we get with the other ideas.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Sabino Mullane 2025-02-21 22:33:43 PATCH: warn about, and deprecate, clear text passwords
Previous Message Corey Huinker 2025-02-21 22:09:42 Re: Statistics Import and Export