| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Alexander Kukushkin <cyberdemn(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Speeding up pg_upgrade |
| Date: | 2017-12-07 19:13:31 |
| Message-ID: | CAKFQuwZDbbTUP7513J6J6dcEEQo_Ny++wDmAz8+69BU9gk=pxg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Dec 7, 2017 at 12:04 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> If you've
> got a better idea for that, great, but having certain pg_upgrade
> migrations require running ANALYZE and some migrations not require it is
> something we need to make users *very* clear about. No, I don't think a
> note in the release notes is really enough..
>
Ideally this would be covered by:
"""
13. Post-Upgrade processing
If any post-upgrade processing is required, pg_upgrade will issue warnings
as it completes. It will also generate script files that must be run by the
administrator. The script files will connect to each database that needs
post-upgrade processing. Each script should be run using: ...
"""
https://www.postgresql.org/docs/10/static/pgupgrade.html
Then whether is instructed as per #14 would be conditional.
Its arguable whether a warning/notice that "ANALYZE doesn't need to be run"
message would be useful.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2017-12-07 19:28:47 | Re: Speeding up pg_upgrade |
| Previous Message | Tom Lane | 2017-12-07 19:09:47 | Re: Speeding up pg_upgrade |