| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Dave Cramer <davecramer(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_upgrade does not upgrade pg_stat_statements properly |
| Date: | 2021-07-29 18:38:57 |
| Message-ID: | CAKFQuwZxwk10EyGzfH3Rh0=K-DAURk1qXTwd2j1nMttOPM2SqA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jul 29, 2021 at 11:35 AM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> Oh, and you can't use the same installation procedures as when you
> installed the extension because that probably included CREATE EXTENSION.
> This really highlights why this is tricky to explain --- we need the
> binaries, but not the SQL that goes with it.
>
Maybe...but the fact that "installation to the O/S" is cluster-wide and
"CREATE EXTENSION" is database-specific I believe this will generally take
care of itself in practice, especially if we leave the part (but ignore any
installation instructions that advise executing create extension).
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yura Sokolov | 2021-07-29 18:55:30 | Re: [PoC] Improve dead tuple storage for lazy vacuum |
| Previous Message | David G. Johnston | 2021-07-29 18:36:58 | Re: pg_upgrade does not upgrade pg_stat_statements properly |