Re: Add starelid, attnum to pg_stats and leverage this in pg_dump - Mailing list pgsql-hackers

From Sami Imseih
Subject Re: Add starelid, attnum to pg_stats and leverage this in pg_dump
Date
Msg-id CAA5RZ0uTxOgN-sfQMV5-3dwE9SqgS3_xf5zhj0Gp12TJtBuk5g@mail.gmail.com
Whole thread
In response to Re: Add starelid, attnum to pg_stats and leverage this in pg_dump  (Corey Huinker <corey.huinker@gmail.com>)
Responses Re: Add starelid, attnum to pg_stats and leverage this in pg_dump
List 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)



pgsql-hackers by date:

Previous
From: Corey Huinker
Date:
Subject: Re: Add starelid, attnum to pg_stats and leverage this in pg_dump
Next
From: Madhav Madhusoodanan
Date:
Subject: Re: [WiP] B-tree page merge during vacuum to reduce index bloat