Re: [HACKERS] SQL procedures - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: [HACKERS] SQL procedures
Date
Msg-id CAEepm=0y+wuYwJvpBa5S-wsV9ukLfyxujshtUa2_Z6WzNivFMg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] SQL procedures  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: [HACKERS] SQL procedures  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On Fri, Dec 1, 2017 at 7:48 AM, Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
> On 11/29/17 14:17, Andrew Dunstan wrote:
>> On 11/28/2017 10:03 AM, Peter Eisentraut wrote:
>>> Here is a new patch that addresses the previous review comments.
>>>
>>> If there are no new comments, I think this might be ready to go.
>>
>> Looks good to me. Marking ready for committer.
>
> committed

postgres=# \df                      List of functionsSchema | Name | Result data type | Argument data types | Type
--------+------+------------------+---------------------+------public | bar  | integer          | i integer           |
funcpublic| foo  |                  | i integer           | proc
 
(2 rows)

Should this now be called a "List of routines"?

-- 
Thomas Munro
http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Arthur Zakirov
Date:
Subject: Re: [HACKERS] Bug in to_timestamp().
Next
From: Robert Haas
Date:
Subject: Re: using index or check in ALTER TABLE SET NOT NULL