| From: | Dave Cramer <davecramer(at)postgres(dot)rocks> |
|---|---|
| To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
| Cc: | Jan Wieck <jan(at)wi3ck(dot)info>, Bruce Momjian <bruce(at)momjian(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-30 10:48:34 |
| Message-ID: | CADK3HHKz4ruqmqiph2cLvg53AibAPsEyen4uDXe1h5bu-nwWjg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 30 Jul 2021 at 06:39, Julien Rouhaud <rjuju123(at)gmail(dot)com> wrote:
> On Fri, Jul 30, 2021 at 06:03:50AM -0400, Dave Cramer wrote:
> >
> > What would happen if subsequent to the upgrade "ALTER EXTENSION UPGRADE"
> > was executed ?
>
> If the extension was already up to date on the source cluster then
> obviously
> nothing.
>
> Otherwise, the extension would be updated. But unless I'm willing (and
> remember) to copy/paste until the end of time an anonymous block code that
> checks the current server version to see if the wrapper function needs to
> be
> overwritten then nothing will happen either as far as this function is
> concerned.
>
Well I think that's on the extension author to fix. There's only so much
pg_upgrade can do here.
It seems reasonable that upgrading the extension should upgrade the
extension to the latest version.
Dave
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lætitia Avrot | 2021-07-30 10:55:42 | Re: pg_dump new feature: exporting functions only. Bad or good idea ? |
| Previous Message | Julien Rouhaud | 2021-07-30 10:39:45 | Re: pg_upgrade does not upgrade pg_stat_statements properly |