| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_upgrade --check fails to warn about abstime |
| Date: | 2023-09-22 03:18:41 |
| Message-ID: | 910187.1695352721@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Wed, Sep 20, 2023 at 06:54:24PM +0200, Álvaro Herrera wrote:
>> I got a complaint that pg_upgrade --check fails to raise red flags when
>> the source database contains type abstime when upgrading from pg11. The
>> type (along with reltime and tinterval) was removed by pg12.
> Wow, I never added code to pg_upgrade to check for that, and no one
> complained either.
Yeah, so most people had indeed listened to warnings and moved away
from those datatypes. I'm inclined to think that adding code for this
at this point is a bit of a waste of time.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lepikhov Andrei | 2023-09-22 03:48:38 | Re: [PoC] Reducing planning time when tables have many partitions |
| Previous Message | Andy Fan | 2023-09-22 03:02:25 | Re: Questioning an errcode and message in jsonb.c |