| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Cc: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Subject: | Re: [HACKERS] SQL procedures |
| Date: | 2017-12-01 14:31:32 |
| Message-ID: | ac653dd2-4ed7-2627-bffd-ffe0703e87bb@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/30/17 15:50, Thomas Munro wrote:
> postgres=# \df
> List of functions
> Schema | Name | Result data type | Argument data types | Type
> --------+------+------------------+---------------------+------
> public | bar | integer | i integer | func
> public | foo | | i integer | proc
> (2 rows)
>
> Should this now be called a "List of routines"?
Maybe, but I hesitate to go around and change all mentions of "function"
like that. That might just confuse people.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexey Kondratov | 2017-12-01 14:33:04 | Re: [HACKERS] GSOC'17 project introduction: Parallel COPY execution with errors handling |
| Previous Message | Peter Eisentraut | 2017-12-01 14:28:08 | Re: [HACKERS] pg_basebackup --progress output for batch execution |