Re: [HACKERS] removing abstime, reltime, tinterval.c, spi/timetravel - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] removing abstime, reltime, tinterval.c, spi/timetravel
Date
Msg-id 23860.1539291422@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] removing abstime, reltime, tinterval.c, spi/timetravel  (Andres Freund <andres@anarazel.de>)
Responses Re: [HACKERS] removing abstime, reltime, tinterval.c, spi/timetravel  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> I've done that now, together with two commits for removal of timetravel
> and abstime, reltime, tinterval.

Unsurprisingly-in-retrospect, buildfarm member crake is now bitching
that cross-version pg_upgrade fails, since it's trying to test importing
back-branch regression DBs that contain tables with the desupported types.

Perhaps the best fix for this is to teach the cross-version-upgrade
buildfarm module to drop the affected tables from the old DB before
testing pg_upgrade.  However, that does nothing to help manual testing
of similar scenarios.

Another idea would be to put table drops into the back branch regression
tests, so that their ending states don't include any such tables.  That
would cripple pg_dump testing of these types in the back branches, but
I'm not sure if we really care much.

I don't especially like either of these choices --- anyone got another
idea?

            regards, tom lane


pgsql-hackers by date:

Previous
From: Dmitry Dolgov
Date:
Subject: Re: [HACKERS] [PATCH] Generic type subscripting
Next
From: Andres Freund
Date:
Subject: Re: [HACKERS] removing abstime, reltime, tinterval.c, spi/timetravel