| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
| Cc: | Matt Peterson <matt(at)caldera(dot)com>, dz(at)cs(dot)unitn(dot)it, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: SEGV in contrib/array/array_iterator.c |
| Date: | 2002-04-02 20:22:05 |
| Message-ID: | 27429.1017778925@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> writes:
> Are the array iterator functions supposed to act sort of like
> =ANY/=ALL except across an array instead of a subselect?
Seems like a reasonable definition.
> If so,
> isStrict probably isn't right, since for an empty subselect the return
> value does not depend on the element being searched for.
Hm ... isn't it NULL anyway, if the left side is NULL?
But if you're right, then the correct fix involves updating the
functions to V1 calling conventions, so that they can make a correct
test for NULL inputs (rather than bogusly checking for zero value).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2002-04-02 20:29:15 | Re: SEGV in contrib/array/array_iterator.c |
| Previous Message | Stephan Szabo | 2002-04-02 20:05:48 | Re: SEGV in contrib/array/array_iterator.c |