diff options
| author | David Rowley <drowley@postgresql.org> | 2022-07-13 15:03:47 +1200 |
|---|---|---|
| committer | David Rowley <drowley@postgresql.org> | 2022-07-13 15:03:47 +1200 |
| commit | c23e3e6beb273ae8c0f8e616edb7ed1acb0271c4 (patch) | |
| tree | b0e092c52196ba79555157a75b498b4ea9b8c4d9 /src/backend/parser/parse_expr.c | |
| parent | 50e4c280f0661f3ef837d2c3beb5fcc100202324 (diff) | |
| download | postgresql-c23e3e6beb273ae8c0f8e616edb7ed1acb0271c4.tar.gz postgresql-c23e3e6beb273ae8c0f8e616edb7ed1acb0271c4.zip | |
Use list_copy_head() instead of list_truncate(list_copy(...), ...)
Truncating off the end of a freshly copied List is not a very efficient
way of copying the first N elements of a List.
In many of the cases that are updated here, the pattern was only being
used to remove the final element of a List. That's about the best case
for it, but there were many instances where the truncate trimming the List
down much further.
4cc832f94 added list_copy_head(), so let's use it in cases where it's
useful.
Author: David Rowley
Discussion: https://postgr.es/m/1986787.1657666922%40sss.pgh.pa.us
Diffstat (limited to 'src/backend/parser/parse_expr.c')
0 files changed, 0 insertions, 0 deletions