| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Support --include-analyze in pg_dump, pg_dumpall, pg_restore |
| Date: | 2025-01-14 16:23:01 |
| Message-ID: | Z4aPZWJ7E-EsnYlm@nathan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 14, 2025 at 09:32:19AM -0500, Tom Lane wrote:
> jian he <jian(dot)universality(at)gmail(dot)com> writes:
>> the implemented feature is as the $subject description, making pg_dump
>> also includes the ANALYZE command in its output.
>
> Isn't this pretty much obsoleted by the ongoing work to dump and
> restore statistics?
Yeah, and I believe that work is still on track for v18. That's likely
going to be much faster than analyzing everything, and it'll be usable in
pg_upgrade, too.
https://postgr.es/m/flat/CADkLM%3DcB0rF3p_FuWRTMSV0983ihTRpsH%2BOCpNyiqE7Wk0vUWA%40mail.gmail.com
--
nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2025-01-14 16:29:53 | Re: pgbench error: (setshell) of script 0; execution of meta-command failed |
| Previous Message | Yugo NAGATA | 2025-01-14 16:21:41 | Re: psql: Add leakproof field to \dAo+ meta-command results |