| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Dave Cramer <davecramer(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, 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 22:26:01 |
| Message-ID: | 20210729222601.GX9600@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jul 29, 2021 at 06:19:56PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > I think we need to first give clear instructions on how to find out if
> > an extension update is available, and then how to update it. I am
> > thinking we should supply a query which reports all extensions that can
> > be upgraded, at least for contrib.
>
> I suggested awhile ago that pg_upgrade should look into
> pg_available_extensions in the new cluster, and prepare
> a script with ALTER EXTENSION UPDATE commands for
> anything that's installed but is not the (new cluster's)
> default version.
I can do that, but I would think a pg_dump/restore would also have this
issue, so should this be more generic? If we had a doc section about
that, we could add it a step to run in the pg_upgrade instructions.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
If only the physical world exists, free will is an illusion.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-07-29 22:29:11 | Re: pg_upgrade does not upgrade pg_stat_statements properly |
| Previous Message | Tom Lane | 2021-07-29 22:19:56 | Re: pg_upgrade does not upgrade pg_stat_statements properly |