From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Retiring support for pre-7.3 FK constraint triggers |
Date: | 2020-03-05 20:50:29 |
Message-ID: | 23394.1583441429@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> On 2020-Mar-05, Tom Lane wrote:
>> As long as we're thinking of zapping code that is long past its sell-by
>> date, I propose getting rid of this stanza in indexcmds.c, which
>> basically causes CREATE INDEX to ignore certain opclass specifications:
> I agree, this should be fine to remove.
Done.
>> which dates to 8.2 (2a8d3d83e of 2005-11-07). This is less bad than the
>> other thing, since it won't affect the behavior of any command that
>> wouldn't otherwise just fail; but maybe its time has passed as well?
>> Although Alvaro's point comparing these behaviors to pg_dump's support
>> cutoff of 8.0 suggests that maybe we should leave this one for now.
> Yeah, dunno, 'rtree' is even immortalized in tests; commit f2e403803fe6
> as recently as March 2019 was seen modifying that.
Hah, I didn't realize we actually had code coverage for that!
> I guess we can wait a couple years more on that one, since it's not
> damaging anything anyway.
Agreed, I left it be.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-03-05 20:52:43 | Re: Retiring support for pre-7.3 FK constraint triggers |
Previous Message | Robert Haas | 2020-03-05 20:48:52 | Re: [HACKERS] Moving relation extension locks out of heavyweight lock manager |