Horton

Re: Retiring support for pre-7.3 FK constraint triggers

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-03-05T20:52:43Z
Lists: pgsql-hackers 
Daniel Gustafsson <daniel@yesql.se> writes:
> Having code which is untested and not excercised by developers (or users, if my
> assumption holds), yet being reachable by SQL, runs the risk of introducing
> subtle bugs.  Is there a usecase for keeping it, or can/should it be removed in
> 14?  That would still leave a lot of supported versions to upgrade to in case
> there are users to need this.

Pushed.  Looking at the original commit, I noticed one now-obsolete
comment that should also be removed, so I did that.

			regards, tom lane

Commits

  1. Remove ancient hacks to ignore certain opclass names in CREATE INDEX.

  2. Remove ancient support for upgrading pre-7.3 foreign key constraints.

  3. Support for INCLUDE attributes in GiST indexes

  4. Remove pg_dump/pg_dumpall support for dumping from pre-8.0 servers.

  5. Teach CREATE CONSTRAINT TRIGGER to convert old-style foreign key