| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Robert Treat <rob(at)xzilla(dot)net>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Remove array_nulls? |
| Date: | 2015-12-18 17:10:33 |
| Message-ID: | 19644.1450458633@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> Not entirely sure what to make of this. It occurs to me that the "it
> breaks immutability" argument might apply to array_nulls, though I've
> not done any legwork to confirm or disprove that. If it doesn't apply,
> though, I'm leaning to the position that there's no reason to remove
> array_nulls.
OK, I went and looked. Array_nulls is consulted only in array_in(),
which is marked stable (and would need to be so marked even without
this consideration, since the array element type's input function
might only be stable). So it's not breaking any rules.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-12-18 17:10:41 | Re: Freeze avoidance of very large table. |
| Previous Message | Andres Freund | 2015-12-18 17:10:14 | Re: Remove array_nulls? |