| commit | 4c40995f61227c579bd7269a829c00013ac66492 | |
| author | Tom Lane <tgl@sss.pgh.pa.us> | |
| Thu, 4 May 2023 15:48:23 +0000 (4 11:48 -0400) | ||
| committer | Tom Lane <tgl@sss.pgh.pa.us> | |
| Thu, 4 May 2023 15:48:23 +0000 (4 11:48 -0400) | ||
| tree | bba6e912c1d3a721a0327c9c78fa409b288c436e | treesnapshot (tar.gz zip) |
| parent | 0553528e7c2bb9eb4148ff9e3c51b9094ab67f70 | commitdiff |
In array_position()/array_positions(), beware of empty input array.
These functions incautiously fetched the array's first lower bound
even when the array is zero-dimensional, thus fetching the word
after the allocated array space. While almost always harmless,
with very bad luck this could result in SIGSEGV. Fix by adding
an early exit for empty input.
Per bug #17920 from Alexander Lakhin.
Discussion: https://postgr.es/m/17920-f7c228c627b6d02e%40postgresql.org
These functions incautiously fetched the array's first lower bound
even when the array is zero-dimensional, thus fetching the word
after the allocated array space. While almost always harmless,
with very bad luck this could result in SIGSEGV. Fix by adding
an early exit for empty input.
Per bug #17920 from Alexander Lakhin.
Discussion: https://postgr.es/m/17920-f7c228c627b6d02e%40postgresql.org
| src/backend/utils/adt/array_userfuncs.c | diffblobblamehistory |