From: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
Subject: | Re: [PATCH] Add get_bytes() and set_bytes() functions |
Date: | 2024-10-18 14:20:42 |
Message-ID: | CAJ7c6TN81pnUFJ3BAZM--3au54Tkk7Sn0uZafF+b4X9863a1Gg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
> > I guess there are in fact two problems, not one.
> >
> > 1. Converting between bytea and integer types
> > 2. Multibyte versions of get_byte() / set_byte()
> >
> > As you rightly pointed out, for (1) we just need to add missing casts.
> > Here is the corresponding patch, v3-0001. Note that I couldn't re-use
> > int{2,4,8}recv because its first argument is StringInfo, so I ended up
> > implementing my own bytea->int{2,4,8} functions.
> >
> > I think there may be value in (2) as well. It's implemented in v3-0002
> > and I did my best to clarify the commit message. On the flip side the
> > situation when one wants something like extracting int4 from a
> > bytea(or vice versa) and is not happy with convenience and/or
> > performance of substr()+casts is arguably rare. I'll be fine with
> > whatever consensus the community reaches about this patch.
>
> PFA the rebased patch set v4.
Rebased, v5.
--
Best regards,
Aleksander Alekseev
Attachment | Content-Type | Size |
---|---|---|
v5-0001-Allow-casting-between-bytea-and-integer-types.patch | application/octet-stream | 8.8 KB |
v5-0002-Add-get_bytes-and-set_bytes-functions.patch | application/octet-stream | 9.9 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-10-18 14:22:32 | Re: Incorrect comment on pg_shadow view |
Previous Message | Matthias van de Meent | 2024-10-18 13:56:53 | Re: Recovery of .partial WAL segments |