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

From Andres Freund
Subject Re: [HACKERS] removing abstime, reltime, tinterval.c, spi/timetravel
Date
Msg-id 20181009232706.vtoqz65rei2tsyik@alap3.anarazel.de
Whole thread Raw
In response to Re: [HACKERS] removing abstime, reltime, tinterval.c, spi/timetravel  (Mark Dilger <hornschnorter@gmail.com>)
Responses Re: [HACKERS] removing abstime, reltime, tinterval.c, spi/timetravel  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hi,

On 2018-10-09 16:17:44 -0700, Mark Dilger wrote:
> > On Oct 9, 2018, at 12:22 PM, Andres Freund <andres@anarazel.de> wrote:
> > As discussed below (at [1]), I think we should remove $subject.  I plan
> > to do so, unless somebody protests soon-ish.  I thought it'd be better
> > to call attention to this in a new thread, to make sure people had a
> > chance to object.
> 
> I have no objection, but I'm curious, when retiring a datatype and
> associated functions, do the Oids that were assigned to them become
> available for new uses, or do you have to expire them to avoid breaking
> pg_upgrade and such?  Retiring built-in types and functions seems
> rare enough that I've not seen how this is handled before.

I don't really see a need for preserving them. pg_upgrade should fail
because the schema dump won't restore (as that has textual oids). You
could argue that external drivers could have the oids builtin, but I
don't find that convincing, because they'd be in trouble for new types
etc anyway.

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Mark Dilger
Date:
Subject: Re: [HACKERS] removing abstime, reltime, tinterval.c, spi/timetravel
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] removing abstime, reltime, tinterval.c, spi/timetravel