Re: Improve tab completion for ALTER FUNCTION/PROCEDURE/ROUTINE - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Improve tab completion for ALTER FUNCTION/PROCEDURE/ROUTINE
Date
Msg-id Y3wX09yd0TKKJ1Wj@paquier.xyz
Whole thread Raw
In response to Re: Improve tab completion for ALTER FUNCTION/PROCEDURE/ROUTINE  (vignesh C <vignesh21@gmail.com>)
Responses Re: Improve tab completion for ALTER FUNCTION/PROCEDURE/ROUTINE
List pgsql-hackers
On Fri, Oct 28, 2022 at 05:34:37PM +0530, vignesh C wrote:
> Those also should be handled, attached v2 version includes the changes
> for the same.

The basic options supported by PROCEDURE are a subset of ROUTINE with a
difference of COST, IMMUTABLE, [NOT] LEAKPROOF, ROWS, STABLE
and VOLATILE.

The basic options supported by ROUTINE are a subset of FUNCTION with a
difference of { CALLED | RETURNS NULL } ON NULL INPUT, STRICT and
SUPPORT.  Is it worth refactoring a bit with common lists?

+       "RESET", "RETURNS NULL ON NULL INPUT ", "ROWS",
Extra space after INPUT here, that's easy to miss.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Error-safe user functions
Next
From: Nathan Bossart
Date:
Subject: wake up logical workers after ALTER SUBSCRIPTION