From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Fontana Daniel C. \(Desartec S.R.L.\)" <desartecsrl@gmail.com>
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: function to_char
In-reply-to: <001b01d7339a$c42a84e0$4c7f8ea0$@gmail.com>
References: <001b01d7339a$c42a84e0$4c7f8ea0$@gmail.com>
Comments: In-reply-to "Fontana Daniel C. \(Desartec S.R.L.\)"
 <desartecsrl@gmail.com>
	message dated "Sat, 17 Apr 2021 12:03:02 -0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <256547.1618672193.1@sss.pgh.pa.us>
Date: Sat, 17 Apr 2021 11:09:53 -0400
Message-ID: <256548.1618672193@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/256548.1618672193%40sss.pgh.pa.us>
Precedence: bulk

"Fontana Daniel C. \(Desartec S.R.L.\)" <desartecsrl@gmail.com> writes:
> Example, select length (to_char (1, '990'))
> returns 4 because?

Per the fine manual:

    * If no explicit provision is made for a sign in to_char()'s pattern,
      one column will be reserved for the sign, and it will be anchored to
      (appear just left of) the number. If S appears just left of some
      9's, it will likewise be anchored to the number.

If you don't want to leave space for a sign, it looks like FM is
the only way to do that.

			regards, tom lane