From: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Peter Eisentraut <peter(at)eisentraut(dot)org> |
Subject: | Re: [PATCH] Add get_bytes() and set_bytes() functions |
Date: | 2025-01-13 17:35:59 |
Message-ID: | CAJ7c6TMtFDQEYOD3i7sypCo7AFez418RVYuR3gzXaLq6QxwvKA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Michael,
> v5-0001 includes the following output:
>
> --- a/src/test/regress/expected/opr_sanity.out
> +++ b/src/test/regress/expected/opr_sanity.out
> @@ -126,9 +126,12 @@ WHERE p1.oid < p2.oid AND
> p1.proretset != p2.proretset OR
> p1.provolatile != p2.provolatile OR
> p1.pronargs != p2.pronargs);
> - oid | proname | oid | proname
> ------+---------+-----+---------
> -(0 rows)
> + oid | proname | oid | proname
> +------+----------+------+---------
> + 2405 | int2send | 8577 | bytea
> + 2407 | int4send | 8578 | bytea
> + 2409 | int8send | 8579 | bytea
> +(3 rows)
>
> This should not happen, as you are using multiple times the same
> function.
Thanks. Here is the corrected patch.
Besides fixing opr_sanity test I corrected error messages:
-ERROR: bytea size 3 out of valid range, 0..2
+ERROR: bytea out of valid range, ''..'\xFFFF'
... and also included tests for min/max integer values.
I discarded the 0002 patch that implemented get_bytes() / set_bytes().
This part doesn't seem to get much support, so let's focus on casting.
--
Best regards,
Aleksander Alekseev
Attachment | Content-Type | Size |
---|---|---|
v6-0001-Allow-casting-between-bytea-and-integer-types.patch | application/x-patch | 9.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Dean Rasheed | 2025-01-13 18:15:15 | Re: Virtual generated columns |
Previous Message | Michail Nikolaev | 2025-01-13 17:31:04 | Re: Conflict Detection and Resolution |