| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
| Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: SQL-level pg_datum_image_equal |
| Date: | 2026-03-25 21:51:02 |
| Message-ID: | CAApHDvo0D4HjEGWZ8XJ0RBOFzo7wZs7r9DogrhnH_Hq7gNRBQQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 26 Mar 2026 at 10:25, Matthias van de Meent
<boekewurm+postgres(at)gmail(dot)com> wrote:
> I'm happy to mark this function as STABLE for now (to prevent its
> inclusion in permanent storage), and/or to adjust the code to adjust
> for subnormal inputs (values with incorrect/inconsistent/unexpected
> sign extensions).
You lost me at this part. How does marking the function as STABLE
prevent users from persisting things on disk based on the return value
of the function? I expected the primary use case for this would be in
trigger functions that make decisions about data that goes into
tables.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sami Imseih | 2026-03-25 21:52:54 | Re: dshash_find_or_insert vs. OOM |
| Previous Message | Melanie Plageman | 2026-03-25 21:34:33 | Re: Buffer locking is special (hints, checksums, AIO writes) |