| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SQL procedures |
| Date: | 2017-10-31 18:23:04 |
| Message-ID: | 9388.1509474184@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> I've been working on SQL procedures.
No comment yet on the big picture here, but ...
> The provided procedural languages (an ever more
> confusing term) each needed a small touch-up to handle pg_proc entries
> with prorettype == 0.
Putting 0 in prorettype seems like a pretty bad idea. Why not use VOIDOID
for the prorettype value? Or if there is some reason why "void" isn't the
right pseudotype, maybe you should invent a new one, analogous to the
"trigger" and "event_trigger" pseudotypes.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-10-31 19:09:11 | Re: Re: PANIC: invalid index offnum: 186 when processing BRIN indexes in VACUUM |
| Previous Message | Alvaro Herrera | 2017-10-31 18:10:53 | Re: Re: PANIC: invalid index offnum: 186 when processing BRIN indexes in VACUUM |