From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Gram <peter.m.gram@gmail.com>
cc: Sbob <sbob@quadratum-braccas.com>,
        Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: char column with a single space as the default not working
In-reply-to: 
 <CAJ=80GV3NaKeRi9GDXa+bA-Zck0YYHwGa90v70GBwoyi1EQftQ@mail.gmail.com>
References: <f7b61d30-3b95-463a-9627-fed806e5e2db@quadratum-braccas.com>
 <CAJ=80GV3NaKeRi9GDXa+bA-Zck0YYHwGa90v70GBwoyi1EQftQ@mail.gmail.com>
Comments: In-reply-to Peter Gram <peter.m.gram@gmail.com>
	message dated "Thu, 30 Nov 2023 18:44:34 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <507458.1701374156.1@sss.pgh.pa.us>
Date: Thu, 30 Nov 2023 14:55:56 -0500
Message-ID: <507459.1701374156@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/507459.1701374156%40sss.pgh.pa.us>
Precedence: bulk

Peter Gram <peter.m.gram@gmail.com> writes:
> I think it behaves as expected. Look at my select "select
> encode(charcol::bytea, 'hex') , intcol from z;" it returns 20 which is a
> space in hex

Yeah, the space is stored.  What is probably surprising the OP
is that applying the || operator involves a coercion from "char"
to "text", which strips the defined-to-be-insignificant trailing
space(s) of the "char" value.

As David said, you're best off not using the char type.
The semantics around trailing spaces are too squishy for
my taste, and there's no real advantage compared to varchar
or text.

			regards, tom lane