From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Luiz E. P. Fernandes" <lepfer@uol.com.br>
cc: pgsql-interfaces@postgresql.org
Subject: Re: Seconds precision in timestamp columns
In-reply-to: <187cc78d-fc34-aaa9-aeb0-f0045b9b4ce8@uol.com.br>
References: <187cc78d-fc34-aaa9-aeb0-f0045b9b4ce8@uol.com.br>
Comments: In-reply-to "Luiz E. P. Fernandes" <lepfer@uol.com.br>
	message dated "Fri, 16 Jul 2021 16:03:53 -0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <56083.1626530651.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Sat, 17 Jul 2021 10:04:11 -0400
Message-ID: <56084.1626530651@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/56084.1626530651%40sss.pgh.pa.us>
Precedence: bulk

"Luiz E. P. Fernandes" <lepfer@uol.com.br> writes:
> In the dvdrental example database, there is a column named 
> 'payment_date' on the 'payment' table and columns 'rental_date' and 
> 'return_date' on the 'rental' table.  These columns appear on the 
> information_schema.columns view with identical specifications: datatype 
> = 'timestamp without timezone', datetime_precision = 6. However, a 
> select on table 'payment' presents column 'payment_date' with 6 
> fractional digits, while a select on table 'rental' presents columns 
> 'rental_date' and 'return_date' without fractional digits.

Presumably this is just an artifact of the example data.  timestamptz_out
suppresses trailing fractional zeroes, regardless of the column's nominal
precision.  So there's no reason to think that one column is being treated
differently from the others.

			regards, tom lane