Re: [PATCH] Tab complete EXECUTE FUNCTION for CREATE (EVENT) TRIGGER

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: ilmari(at)ilmari(dot)org (Dagfinn Ilmari =?utf-8?Q?Manns=C3=A5ker?=)
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, David Fetter <david(at)fetter(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] Tab complete EXECUTE FUNCTION for CREATE (EVENT) TRIGGER
Date: 2018-10-26 14:13:20
Message-ID: 25993.1540563200@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

ilmari(at)ilmari(dot)org (Dagfinn Ilmari =?utf-8?Q?Manns=C3=A5ker?=) writes:
> A related issue is whether we should change pg_get_triggerdef() to emit
> the new syntax as well (in HEAD only, since it would break things that
> parse the output).

No, because pg_get_triggerdef() does not know what its output will be
used for. We can probably change that five years down the road, but
right now it could be expected to break reasonable use-cases.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-10-26 14:20:02 Re: Should pg 11 use a lot more memory building an spgist index?
Previous Message Alvaro Herrera 2018-10-26 14:09:27 Re: Should pg 11 use a lot more memory building an spgist index?