Re: [PATCH] Add get_bytes() and set_bytes() functions
| От | Joel Jacobson |
|---|---|
| Тема | Re: [PATCH] Add get_bytes() and set_bytes() functions |
| Дата | |
| Msg-id | 7882ebcf-4f1f-4f57-afeb-e1301dd6c9d3@app.fastmail.com обсуждение |
| Ответ на | [PATCH] Add get_bytes() and set_bytes() functions (Aleksander Alekseev <aleksander@timescale.com>) |
| Ответы |
Re: [PATCH] Add get_bytes() and set_bytes() functions
|
| Список | pgsql-hackers |
On Wed, Aug 14, 2024, at 13:01, Aleksander Alekseev wrote: > The proposed patch adds get_bytes() and set_bytes() functions. The > semantics is similar to get_byte() and set_byte() we already have but > the functions operate with bigints rather than bytes and the user can > specify the size of the integer. This allows working with int2s, > int4s, int8s or even int5s if needed. +1 I wanted this myself many times. I wonder if get_bytes() and set_bytes() will behave differently on little-endian vs big-endian systems? If so, then I think it would be nice to enforce a consistent byte order (e.g., big-endian), to ensure consistent behavior across platforms. Regards, Joel
В списке pgsql-hackers по дате отправления: