Re: zero char is returned as space

From: Konstantin Izmailov <pgfizm(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: zero char is returned as space
Date: 2022-04-06 05:23:53
Message-ID: CAAw-MsdCAPCz07UZcL-bCV=Whcww5oS2E5Sqoju0qeuty65fJw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom,
thank you very much! It makes sense now.

K

On Tue, Apr 5, 2022 at 10:08 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Konstantin Izmailov <pgfizm(at)gmail(dot)com> writes:
> > could you help me understand if this is an intended behaviour, or I'm
> > incorrectly querying a "char" field?
>
> We do not support '\0' as an element of a string value. You didn't
> show how you're trying to insert this value, but I suspect that
> Postgres saw it as an empty string which it then space-padded to
> length 1 because that's what char(1) does.
>
> Don't use a string field to store an integer. What with the need
> for a length header, you wouldn't be saving any space compared to
> "smallint" even if there weren't any semantic issues.
>
> regards, tom lane
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2022-04-06 05:30:37 Re: API stability
Previous Message Amit Kapila 2022-04-06 05:19:40 Perform streaming logical transactions by background workers and parallel apply