| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Dave Cramer <davecramer(at)gmail(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(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 15:42:16 |
| Message-ID: | 20210729154216.GL9600@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jul 29, 2021 at 11:36:19AM -0400, Dave Cramer wrote:
>
>
> I have an issue with the fragment "whether they are from contrib" - my
> understanding at this point is that because of the way we package and
> version contrib it should not be necessary to copy those shared object
> files from the old to the new server (maybe, just maybe, with a
> qualification that you are upgrading between two versions that were in
> support during the same time period).
>
>
> Just to clarify. In no case are binaries copied from the old server to the new
> server. Whether from contrib or otherwise.
Right. Those are _binaries_ and therefore made to match a specific
Postgres binary. They might work or might not, but copying them is
never a good idea --- they should be recompiled to match the new server
binary, even if the extension had no version/API changes.
--
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 | Jan Wieck | 2021-07-29 15:46:12 | Re: pg_upgrade does not upgrade pg_stat_statements properly |
| Previous Message | Bruce Momjian | 2021-07-29 15:40:27 | Re: pg_upgrade does not upgrade pg_stat_statements properly |