|From:||Daniel Gustafsson <daniel(at)yesql(dot)se>|
|To:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|Cc:||Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>|
|Subject:||Re: Retiring support for pre-7.3 FK constraint triggers|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
> On 5 Mar 2020, at 21:52, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Daniel Gustafsson <daniel(at)yesql(dot)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.
Thanks, I was looking around but totally missed that comment.
|Next Message||Aleksei Ivanov||2020-03-05 23:27:05||Re: Proposal: PqSendBuffer removal|
|Previous Message||Tom Lane||2020-03-05 23:08:27||Re: Allowing ALTER TYPE to change storage strategy|