| 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>, 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-15 16:16:09 |
| Message-ID: | CADK3HHLEHr=q8Wd01Osstu3=iiTXP8Q_La8LX9-fjFt2MHSL5Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 15 Jul 2021 at 12:13, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
wrote:
> On 2021-Jul-15, Alvaro Herrera wrote:
>
> > On 2021-Jul-15, Dave Cramer wrote:
> >
> > > Well IMHO the status quo is terrible. Perhaps you have a suggestion on
> how
> > > to make it better ?
> >
> > I thought the suggestion of having pg_upgrade emit a file with a list of
> > all extensions needing upgrade in each database was a fairly decent one.
>
> I think this is the minimum we should be doing.
> Eh, and
> pg_upgrade [other switches] --upgrade-extensions
> sounds good too ...
>
Ultimately I believe this is the solution, however we still need to teach
extensions how to upgrade themselves or emit a message saying they can't,
or even ignore if it truly is a NOP.
Dave
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2021-07-15 16:25:37 | Re: pg_upgrade does not upgrade pg_stat_statements properly |
| Previous Message | David G. Johnston | 2021-07-15 16:15:34 | Re: pg_upgrade does not upgrade pg_stat_statements properly |