Re: Patch: shouldn't timezone(text, timestamp[tz]) be STABLE?

From: Aleksander Alekseev <aleksander(at)timescale(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Patch: shouldn't timezone(text, timestamp[tz]) be STABLE?
Date: 2021-08-30 16:09:14
Message-ID: CAJ7c6TNmKF_7vDiNJTVzRUCtMU82FOd6FbszTMMWgX7pKacTDw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Tom,

Thanks for the quick reply.

> I don't see a lot of argument for treating tzdata changes differently
> from OS locale changes.

Got it. But in this case, what's your opinion on the differences between
date_trunc() and timezone()? Shouldn't date_trunc() be always IMMUTABLE as
well?

I can see pros and cons to be IMMUTABLE _or_ STABLE when dealing with time
zones, but at least PostgreSQL should be consistent in this, right?

--
Best regards,
Aleksander Alekseev

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-08-30 16:42:39 Re: Can we get rid of repeated queries from pg_dump?
Previous Message Tomas Vondra 2021-08-30 15:59:50 Re: Use extended statistics to estimate (Var op Var) clauses