Re: [GENERAL] unnest-like pg_stats.most_common_values and pg_stats.most_common_freqs - Mailing list pgsql-general

From Luca Ferrari
Subject Re: [GENERAL] unnest-like pg_stats.most_common_values and pg_stats.most_common_freqs
Date
Msg-id CAKoxK+6BN7BSVKg-aZdFmEMutP+QbyuwN4pftS89ohB-zHTyRw@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] unnest-like pg_stats.most_common_values andpg_stats.most_common_freqs  (Justin Pryzby <pryzby@telsasoft.com>)
Responses Re: [GENERAL] unnest-like pg_stats.most_common_values and pg_stats.most_common_freqs
List pgsql-general
On Fri, Nov 17, 2017 at 9:41 PM, Justin Pryzby <pryzby@telsasoft.com> wrote:
> I think you want something like this ?
>
> postgres=# SELECT schemaname, tablename, attname, unnest(histogram_bounds::text::text[]), histogram_bounds FROM
pg_statsLIMIT 9;
 
>  pg_catalog | pg_pltemplate | tmplname    | plperl              |
{plperl,plperlu,plpgsql,plpython2u,plpython3u,plpythonu,pltcl,pltclu}

I don't think it is what I'm looking for, I would like something ,like:
select unnest( histogram_bounds::text::text[] ), unnest(
most_common_freqs ) from pg_stats

but with correlation between the two array indexes. Is it something
achievable in SQL? Or should I use a plpgsql loop with an index?

Luca


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

pgsql-general by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: [GENERAL] Query Using Massive Temp Space
Next
From: Semler Miloslav
Date:
Subject: Re: [GENERAL] Query Using Massive Temp Space