From: Tom Lane <tgl@sss.pgh.pa.us>
To: memnik@hotmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16238: Function " to_char(timestamp, text) " doesn't work properly
Date: Thu, 30 Jan 2020 11:27:02 -0500
Message-ID: <22130.1580401622@sss.pgh.pa.us> (raw)
In-Reply-To: <16238-3008a3b37b41cb0e@postgresql.org>
References: <16238-3008a3b37b41cb0e@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> As i noticed the problem is that the function "
> to_char(timestamp, text) " doesn't work properly. For example this query "
> select to_char('2020-01-29'::date,'Day') " give me this result "Wednesday",
> but this query " select to_char('2020-01-31'::date,'Day') " give me this
> result "Friday ".
> So, i guess it is not right to have days with many spaces as a result and
> some days without any space.
No, that's behaving as expected and documented. If you don't want
fixed-width output, use the FM prefix:
=# select to_char('2020-01-31'::date,'-Day-');
to_char
-------------
-Friday -
(1 row)
=# select to_char('2020-01-31'::date,'-FMDay-');
to_char
----------
-Friday-
(1 row)
regards, tom lane
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-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, memnik@hotmail.com
Subject: Re: BUG #16238: Function " to_char(timestamp, text) " doesn't work properly
In-Reply-To: <22130.1580401622@sss.pgh.pa.us>
References: <16238-3008a3b37b41cb0e@postgresql.org> <22130.1580401622@sss.pgh.pa.us>
* 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