public inbox for [email protected]
help / color / mirror / Atom feedFrom: Célestin Matte <[email protected]>
To: Magnus Hagander <[email protected]>
Cc: PostgreSQL WWW <[email protected]>
Subject: Re: pglister: issue with materialized view after upgrade (+ solution)
Date: Mon, 9 Oct 2023 14:31:16 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CABUevEw3MaXWAT5pf7EPP_-oFJSpX7FVP0jgf71ps_jWnxPKaA@mail.gmail.com>
References: <[email protected]>
<CABUevEw3MaXWAT5pf7EPP_-oFJSpX7FVP0jgf71ps_jWnxPKaA@mail.gmail.com>
> Hm. I guess the problem here is that `pg_dump -s` creates the view
> WITH NO DATA. But how exactly did you run the upgrade -- a normal
> `pg_dump` of a pglister database will include a `REFRESH MATERIALIZED
> VIEW` command right at the end.
I used pg_upgradecluster with no additional option (sudo -u postgres pg_upgradecluster 12 main).
> This may be an issue in how pg_upgradecluster executes it perhaps?
Do you mean that the issue could be with pg_upgradecluster then?
--
Célestin Matte
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: pglister: issue with materialized view after upgrade (+ solution)
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox