From: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, 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>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
Subject: | Re: Statistics Import and Export |
Date: | 2024-03-15 07:55:13 |
Message-ID: | CADkLM=c94wr-k-Twufg9yW8KB3oSKWHDB_ph5Yvqq=duPH_z-Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
> ANALYZE takes out one lock StatisticRelationId per relation, not per
> attribute like we do now. If we didn't release the lock after every
> attribute, and we only called the function outside of a larger transaction
> (as we plan to do with pg_restore) then that is the closest we're going to
> get to being consistent with ANALYZE.
>
v9 attached. This adds pg_dump support. It works in tests against existing
databases such as dvdrental, though I was surprised at how few indexes have
attribute stats there.
Statistics are preserved by default, but this can be disabled with the
option --no-statistics. This follows the prevailing option pattern in
pg_dump, etc.
There are currently several failing TAP tests around
pg_dump/pg_restore/pg_upgrade. I'm looking at those, but in the mean
time I'm seeking feedback on the progress so far.
Attachment | Content-Type | Size |
---|---|---|
v9-0001-Create-pg_set_relation_stats-pg_set_attribute_sta.patch | text/x-patch | 42.0 KB |
v9-0002-Enable-dumping-of-table-index-stats-in-pg_dump.patch | text/x-patch | 20.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2024-03-15 07:57:25 | Re: Add new error_action COPY ON_ERROR "log" |
Previous Message | Bharath Rupireddy | 2024-03-15 07:42:35 | Be strict when request to flush past end of WAL in WaitXLogInsertionsToFinish |