diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2023-12-27 15:55:46 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2023-12-27 15:55:46 -0500 |
commit | 58054de2d0847c09ef091956f72ae5e9fb9a176e (patch) | |
tree | 509bfa191ff6a4c455b8b7ac269d9acdcb29d4f3 /doc/src | |
parent | 6c361d323b908c0391e05d15afc01957db2e415b (diff) | |
download | postgresql-58054de2d0847c09ef091956f72ae5e9fb9a176e.tar.gz postgresql-58054de2d0847c09ef091956f72ae5e9fb9a176e.zip |
Improve the implementation of information_schema._pg_expandarray().
This function was originally coded with a handmade expansion
of the array subscripts. We can do it a little faster and far
more legibly today, by using unnest() WITH ORDINALITY.
While at it, let's apply the rowcount estimation support that exists
for the underlying unnest() function: reduce the default ROWS estimate
to 100 and attach array_unnest_support. I'm not sure that
array_unnest_support can do anything useful today with the call sites
that exist in information_schema, but it can't hurt, and the existing
default rowcount of 1000 is surely much too high for any of these
cases.
The psql.sql regression script is using _pg_expandarray() as a
test case for \sf+. While we could keep doing so, the new one-line
function body makes a poor test case for \sf+ row-numbering, so
switch it to print another information_schema function.
Discussion: https://postgr.es/m/1424303.1703355485@sss.pgh.pa.us
Diffstat (limited to 'doc/src')
0 files changed, 0 insertions, 0 deletions