From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: array_cat anycompatible change is breaking xversion upgrade tests (v14 release notes) |
Date: | 2021-06-12 01:42:41 |
Message-ID: | 20210612014241.GB23694@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jun 11, 2021 at 08:19:48PM -0500, Justin Pryzby wrote:
> On Fri, Jun 11, 2021 at 09:12:55PM -0400, Bruce Momjian wrote:
> > OK, I used some of your ideas and tried for something more general;
> > patch attached.
>
> This is good.
>
> But I wonder if "dropped before upgrading" is too specific to pg_upgrade?
>
> Dropping the aggregate before starting a backup to be restored into a new
> version seems like a bad way to do it. More likely, I would restore whatever
> backup I had, get errors, and then eventually recreate the aggregates.
I am actually unclear on that. Do people really restore a dump and just
ignore errors, or somehow track them and go back and try to fix them.
Isn't there a cascading effect if other things depend on it? How do
they get the object definitions from a huge dump file? What process
should we recommend? I have just never seen good documentation on how
this handled.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
If only the physical world exists, free will is an illusion.
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2021-06-12 01:44:34 | ProcArrayStruct->pgprocnos vs ->maxProcs vs PGPROC ordering |
Previous Message | Bruce Momjian | 2021-06-12 01:40:07 | Re: array_cat anycompatible change is breaking xversion upgrade tests (v14 release notes) |