| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: CALL versus procedures with output-only arguments |
| Date: | 2021-05-29 17:32:41 |
| Message-ID: | 2142806.1622309561@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Here's a stripped-down patch that drops the change in what should be
in CALL argument lists, and just focuses on reverting the change in
pg_proc.proargtypes and the consequent mess for ALTER/DROP ROUTINE.
I spent some more effort on the docs, too.
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| reconsider-out-args-2.patch | text/x-diff | 73.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2021-05-29 19:23:21 | Re: fdatasync performance problem with large number of DB files |
| Previous Message | Bharath Rupireddy | 2021-05-29 15:49:59 | Re: CREATE COLLATION - check for duplicate options and error out if found one |