| From: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
|---|---|
| To: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
| Cc: | Pg <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: CREATE ROUTINE MAPPING |
| Date: | 2018-01-12 16:11:26 |
| Message-ID: | CADkLM=cn8DbuY_Q-J9=eiv2udKL6h4uMa_4SkBRZRyXVe5a+Kg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
> PostgreSQL allows function overloading, which means that there can be
> multiple functions with same name differing in argument types. So, the
> syntax has to include the input parameters or their types at least.
>
"local_routine_name" and "remote_routine_spec" were my own paraphrasings of
what the spec implies. I'm nearly certain that the local routine name,
which the spec says is just an identifier, cannot have a parameter spec on
it, which leaves only one other place to define it, remote_routine_spec,
which wasn't defined at all. I _suppose_ parameter definitions could be
pushed into options, but that'd be ugly.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2018-01-12 16:14:22 | Re: pgbench - add \if support |
| Previous Message | Tom Lane | 2018-01-12 16:06:22 | Re: improve type conversion of SPI_processed in Python |