Re: Wrong provolatile value for to_timestamp (1 argument)

From: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
To: laurenz(dot)albe(at)cybertec(dot)at
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Wrong provolatile value for to_timestamp (1 argument)
Date: 2022-07-05 10:37:02
Message-ID: 20220705.193702.224557622081525398.t-ishii@sranhm.sra.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2022-07-05 10:50:32 Re: Schema variables - new implementation for Postgres 15
Previous Message Dagfinn Ilmari Mannsåker 2022-07-05 09:27:54 Re: [PATCH] Add result_types column to pg_prepared_statements view