From: | Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Avoid is possible a expensive function call (src/backend/utils/adt/varlena.c) |
Date: | 2024-03-05 11:44:15 |
Message-ID: | CAEudQAqjM8nXC6ZAS5z3rfqsXNbdLCZQNc-P-U1TXAs0Qg3JpQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Em seg., 4 de mar. de 2024 às 20:28, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> escreveu:
> Michael Paquier <michael(at)paquier(dot)xyz> writes:
> > On Mon, Mar 04, 2024 at 03:08:03PM -0300, Ranier Vilela wrote:
> >> I can't see any user validation at the function
> pg_newlocale_from_collation.
>
> > Matthias is right, look closer. I can see more than one check,
> > especially note the one related to the collation version mismatch that
> > should not be silently ignored.
>
> The fast path through that code doesn't include any checks, true,
> but the point is that finding the entry proves that we made those
> checks previously. I can't agree with making those semantics
> squishy in order to save a few cycles in the exact-equality case.
>
Robustness is a fair point.
best regards,
Ranier Vilela
From | Date | Subject | |
---|---|---|---|
Next Message | Ashutosh Bapat | 2024-03-05 12:08:30 | Re: SQL Property Graph Queries (SQL/PGQ) |
Previous Message | Richard Guo | 2024-03-05 11:43:21 | Get rid of the excess semicolon in planner.c |