| From: | Alena Rybakina <a(dot)rybakina(at)postgrespro(dot)ru> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: may be a mismatch between the construct_array and construct_md_array comments |
| Date: | 2024-09-14 21:31:07 |
| Message-ID: | 6bbdb5c2-946d-4fe0-96ac-f4d56b6987de@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12.09.2024 20:44, Tom Lane wrote:
> Alena Rybakina <a(dot)rybakina(at)postgrespro(dot)ru> writes:
>> I noticed that there is a comment that values with NULL are not
>> processed there, but in fact this function calls the construct_md_array
>> function, which
>> contains a comment that it can handle NULL values.
> Right. construct_md_array has a "bool *nulls" argument, but
> construct_array doesn't --- it passes NULL for that to
> construct_md_array, which will therefore assume there are no null
> array elements.
>
Understood.
At first I thought this comment was related to the value of a NULL
element that might be in the Array, but now I realized that this is not
the case.
Thanks for the explanation, it helped a lot!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2024-09-14 21:50:09 | Re: Why don't we consider explicit Incremental Sort? |
| Previous Message | Thomas Munro | 2024-09-14 20:45:39 | Re: Robocopy might be not robust enough for never-ending testing on Windows |