From: Rob Sargent <robjsargent@gmail.com>
To: Igor Korot <ikorot01@gmail.com>
Cc: Pavel Stehule <pavel.stehule@gmail.com>
Cc: pgsql-generallists.postgresql.org <pgsql-general@lists.postgresql.org>
Subject: Re: Return trimmed string from the query
Date: Wed, 4 Nov 2026 21:48:09 -0700
Message-ID: <B14DD367-C5E9-4EE9-8F8B-05EF6315430B@gmail.com> (raw)
In-Reply-To: <CA+FnnTwCus_FgF0Q-r_BXBf6V1CDnAV6mbXLK+Ua=Bs7c7MnmA@mail.gmail.com>
References: <CA+FnnTwCus_FgF0Q-r_BXBf6V1CDnAV6mbXLK+Ua=Bs7c7MnmA@mail.gmail.com>
> Sorry for a late reply.
>
> So does this mean that if I use varchar instead of char I will not
> have this problem?
>
> Thank you,
Yes. If you use text rather char(n) you will not get space-padded values.
If you have char(n) fields already you have work to do to irradiate them. It will be effort well spent though.
>
>> (1 row)
>>
>> regards
>>
>> Pavel
>>
>>>
>>>
>>> Thank you.
>>>
>>>
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: robjsargent@gmail.com, ikorot01@gmail.com, pavel.stehule@gmail.com
Subject: Re: Return trimmed string from the query
In-Reply-To: <B14DD367-C5E9-4EE9-8F8B-05EF6315430B@gmail.com>
References: <CA+FnnTwCus_FgF0Q-r_BXBf6V1CDnAV6mbXLK+Ua=Bs7c7MnmA@mail.gmail.com> <B14DD367-C5E9-4EE9-8F8B-05EF6315430B@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox