Re: [PATCH] Add get_bytes() and set_bytes() functions

From: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
To: Aleksander Alekseev <aleksander(at)timescale(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, 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 18:24:37
Message-ID: CAEZATCWNdy4LoWgYGbQSS5B5G1YOgSz+Ok4Ako2-aVP4PSk6Eg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 13 Jan 2025 at 17:36, Aleksander Alekseev
<aleksander(at)timescale(dot)com> wrote:
>
> 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'
>

"smallint out of range", "integer out of range" and "bigint out of
range" would be more consistent with existing error messages.

Regards,
Dean

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2025-01-13 18:54:52 Re: Skip collecting decoded changes of already-aborted transactions
Previous Message vignesh C 2025-01-13 18:21:47 Re: Pgoutput not capturing the generated columns