You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Historically, our `"char"` type has differed from Postgres. We allow
multi-byte UTF-8 characters, while in Postgres `"char"` values are
always a single byte. This inconsistency is difficult to change at this
point.
In #70942 we began truncating `"char"` values to a single byte when
decoding them in pgwire. This caused odd behavior with these values
because the rest of the system truncates `"char"` values to a single
UTF-8 character instead. This commit updates the pgwire decoding to make
it consistent with other SQL logic.
Fixes#149427
Release note (bug fix): Fixes a minor bug that caused inconsistent
behavior with the very rarely used `"char"` type (not to be confused
with `CHAR`).
0 commit comments