Re: [PATCH] Rename trim_array() for consistency with the rest of array_* functions

From: Aleksander Alekseev <aleksander(at)timescale(dot)com>
To: Vik Fearing <vik(at)postgresfriends(dot)org>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] Rename trim_array() for consistency with the rest of array_* functions
Date: 2024-10-29 12:23:15
Message-ID: CAJ7c6TNiWTTj7yXAwu0Jwtv21i9JMsyijp4LAkafzVbix+jGwg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Vik,

> While unfortunately named, we cannot deprecate TRIM_ARRAY() because it
> is mandated by the standard.

I didn't know that, thanks.

Still PostgreSQL doesn't follow the standard precisely in more than
one respect. Perhaps we should add array_trim() and keep both? Or
(less likely) remove trim_array() and document this deviation from the
standard? Or at least document why it's named this way.

What do you think?

--
Best regards,
Aleksander Alekseev

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2024-10-29 12:25:23 Re: Avoid possible useless call to makeNode function (src/backend/commands/view.c)
Previous Message Nikita Malakhov 2024-10-29 12:19:18 Re: detoast datum into the given buffer as a optimization.