| From: | Dave Cramer <davecramer(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, 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 17:15:30 |
| Message-ID: | CADK3HH+BXVH1xDqiubj3Gq7Ue2jcn30dQrqq8+4cf0qwSwkdsw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 29 Jul 2021 at 13:13, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
wrote:
> On 2021-Jul-29, Dave Cramer wrote:
>
> > > If the old cluster used extensions those same extensions must be
> > > installed in the new cluster via installation procedures specific
> > > to, and documented by, each extension. For contrib extensions it is
> > > usually enough to install the -contrib package via the same method
> > > you used to install the PostgreSQL server.
> >
> > Well this is not strictly true. There are many extensions that would
> > work just fine with the current pg_upgrade. It may not even be
> > necessary to recompile them.
>
> It is always necessary to recompile because of the PG_MODULE_MAGIC
> declaration, which is mandatory and contains a check that the major
> version matches. Copying the original shared object never works.
>
Thx, I knew I was on shaky ground with that last statement :)
Dave
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2021-07-29 17:15:53 | Re: [PoC] Improve dead tuple storage for lazy vacuum |
| Previous Message | Alvaro Herrera | 2021-07-29 17:13:48 | Re: pg_upgrade does not upgrade pg_stat_statements properly |