Re: pg_upgrade does not upgrade pg_stat_statements properly

From: Jan Wieck <jan(at)wi3ck(dot)info>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Dave Cramer <davecramer(at)postgres(dot)rocks>
Cc: 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 23:18:10
Message-ID: 5fd9eb09-0cfe-4fe8-3136-2630383e2547@wi3ck.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 7/15/21 4:24 PM, David G. Johnston wrote:

> OK, especially as this seems useful outside of pg_upgrade, and if done
> separately is something pg_upgrade could just run as part of its new
> cluster evaluation scripts.  Knowing whether an extension is outdated
> doesn't require the old cluster.

Knowing that (the extension is outdated) exactly how? Can you give us an
example query, maybe a few SQL snippets explaining what exactly you are
talking about? Because at this point you completely lost me.

Sorry, Jan

--
Jan Wieck

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2021-07-15 23:31:07 Re: pg_upgrade does not upgrade pg_stat_statements properly
Previous Message Mark Dilger 2021-07-15 23:07:46 Re: data corruption hazard in reorderbuffer.c