Re: Add starelid, attnum to pg_stats and leverage this in pg_dump

From: Sami Imseih <samimseih(at)gmail(dot)com>
To: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
Cc: nathandbossart(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Add starelid, attnum to pg_stats and leverage this in pg_dump
Date: 2026-03-05 20:45:25
Message-ID: CAA5RZ0uTxOgN-sfQMV5-3dwE9SqgS3_xf5zhj0Gp12TJtBuk5g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>> I noticed that you changed the tests to selecting individual columns. I am
>> not clear as to why this is better?
>>
>> -SELECT *
>> +SELECT schemaname, tablename, attname, attnum, inherited, null_frac, avg_width,
>> + n_distinct, most_common_vals, most_common_freqs, histogram_bounds,
>> + correlation, most_common_elems, most_common_elem_freqs,
>> + elem_count_histogram, range_length_histogram, range_empty_frac,
>> + range_bounds_histogram

Makes sense.

BTW, I do not see a CF enty for this.

Thanks!

--
Sami Imseih
Amazon Web Services (AWS)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Madhav Madhusoodanan 2026-03-05 20:45:31 Re: [WiP] B-tree page merge during vacuum to reduce index bloat
Previous Message Corey Huinker 2026-03-05 20:40:16 Re: Add starelid, attnum to pg_stats and leverage this in pg_dump