| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_upgrade analyze script |
| Date: | 2020-10-06 20:49:33 |
| Message-ID: | 20201006204933.GC12277@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 6, 2020 at 10:40:30PM +0200, Magnus Hagander wrote:
> I think that's information that belongs in the documentation, for those that
> case. I'm willing to bet that the large majority of the people who run the
> script never read that, and certainly don't cancel it. Those that need it to
> their upgrade planning long before they get to that stage.
>
> It's already decently documented on the vacuumdb page. Maybe just add a link
> to that from the pg_upgrade reference page (https://www.postgresql.org/docs/
> current/pgupgrade.html under point 14)?
Agreed.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-10-06 21:19:53 | Re: pg_dump bug for extension owned tables |
| Previous Message | Magnus Hagander | 2020-10-06 20:41:04 | Re: pg_upgrade dead code for pre-8.4 versions |