Re: The command tag of "ALTER MATERIALIZED VIEW RENAME COLUMN"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Ibrar Ahmed <ibrar(dot)ahmad(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: The command tag of "ALTER MATERIALIZED VIEW RENAME COLUMN"
Date: 2019-11-05 14:19:20
Message-ID: 7577.1572963560@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Fujii Masao <masao(dot)fujii(at)gmail(dot)com> writes:
> I'm thinking to commit the patch. But I have one question; is it ok to
> back-patch? Since the patch changes the command tags for some commands,
> for example, which might break the existing event trigger functions
> using TG_TAG if we back-patch it. Or we should guarantee the compatibility of
> command tag within the same major version?

I would not back-patch this. I don't think it's enough of a bug
to justify taking any compatibility risks for.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2019-11-05 14:19:33 Re: v12 and pg_restore -f-
Previous Message Stephen Frost 2019-11-05 14:11:32 Re: v12 and pg_restore -f-