Re: pg_upgrade does not upgrade pg_stat_statements properly - Mailing list pgsql-hackers

From Dave Cramer
Subject Re: pg_upgrade does not upgrade pg_stat_statements properly
Date
Msg-id CADK3HHJtWQCjbQns2WkrirnAWR7YEP-LjpH5Gup0gf4+P=sH4A@mail.gmail.com
Whole thread Raw
In response to Re: pg_upgrade does not upgrade pg_stat_statements properly  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: pg_upgrade does not upgrade pg_stat_statements properly  ("David G. Johnston" <david.g.johnston@gmail.com>)
Re: pg_upgrade does not upgrade pg_stat_statements properly  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers


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.

Dave

pgsql-hackers by date:

Previous
From: Yura Sokolov
Date:
Subject: Re: [PoC] Improve dead tuple storage for lazy vacuum
Next
From: "David G. Johnston"
Date:
Subject: Re: pg_upgrade does not upgrade pg_stat_statements properly