Re: Wrong provolatile value for to_timestamp (1 argument) - Mailing list pgsql-hackers

From Tatsuo Ishii
Subject Re: Wrong provolatile value for to_timestamp (1 argument)
Date
Msg-id 20220705.193702.224557622081525398.t-ishii@sranhm.sra.co.jp
Whole thread Raw
In response to Re: Wrong provolatile value for to_timestamp (1 argument)  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: Wrong provolatile value for to_timestamp (1 argument)
List pgsql-hackers
> Are you sure?  I'd say that "to_timestamp(double precision)" always
> produces the same timestamp for the same argument.  What changes with
> the setting of "timezone" is how that timestamp is converted to a
> string, but that's a different affair.

Of course the internal representation of timestamp with time zone data
type is not affected by the time zone setting. But why other form of
to_timestamp is labeled as stable? If your theory is correct, then
other form of to_timestamp shouldn't be labeled immutable as well?

Best reagards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp



pgsql-hackers by date:

Previous
From: Dagfinn Ilmari Mannsåker
Date:
Subject: Re: [PATCH] Add result_types column to pg_prepared_statements view
Next
From: Julien Rouhaud
Date:
Subject: Re: Schema variables - new implementation for Postgres 15