Re: [HACKERS] removing abstime, reltime, tinterval.c, spi/timetravel

From: Andres Freund <andres(at)anarazel(dot)de>
To: Mark Dilger <hornschnorter(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] removing abstime, reltime, tinterval.c, spi/timetravel
Date: 2018-10-09 23:27:06
Message-ID: 20181009232706.vtoqz65rei2tsyik@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)anarazel(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-10-10 00:25:33 Re: [HACKERS] removing abstime, reltime, tinterval.c, spi/timetravel
Previous Message Mark Dilger 2018-10-09 23:17:44 Re: [HACKERS] removing abstime, reltime, tinterval.c, spi/timetravel