| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 德哥 <digoal(at)126(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14463: refcursor cann't used with array or variadic parameter? |
| Date: | 2016-12-13 16:49:18 |
| Message-ID: | CAFj8pRDASMcTo9XQ5yrQh2aDjfxUBsWWtW557BPZguSUFR-f=Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
2016-12-13 17:45 GMT+01:00 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> > It is not a bug - it is feature. PLpgSQL statements doesn't expect a
> > expression on some places.
>
> Well, it's not unreasonable to expect that a subscripted datum could
> be used. It looks to me like this is a grammar omission and the
> executor code would work fine.
>
There is only one possible issue - the early type check in compile time
will be moved to late check in runtime.
Maybe it was reason why somebody didn't allowed a expr there.
Regards
Pavel
>
> regards, tom lane
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2016-12-13 19:52:11 | Re: BUG #14464: Problems about FUNCTIONS |
| Previous Message | Tom Lane | 2016-12-13 16:45:31 | Re: BUG #14463: refcursor cann't used with array or variadic parameter? |