Re: Failure of postgres_fdw because of TimeZone setting

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Adnan Dautovic <daut(at)mailbox(dot)org>
Cc: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Failure of postgres_fdw because of TimeZone setting
Date: 2024-04-10 20:21:47
Message-ID: 4170840.1712780507@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Adnan Dautovic <daut(at)mailbox(dot)org> writes:
> On 05. Apr 2024, at 16:13, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Out of curiosity, does
>> SET timezone to 'GMT';
>> work?

> Yes, it yields:
>> SET
>>
>> Query returned successfully in 84 msec.

I expected that, because the name "GMT" is hard-wired in our code.
Doesn't help for postgres_fdw though, because it has "UTC" hardwired.
(I have a todo item to rationalize that...)

> By the way, the row count of pg_timezone_names is 385, but I do
> not know how that compares to a more standard installation.

Using current PG HEAD (with tzdata release 2024a):

=# select count(*) from pg_timezone_names;
count
-------
597
(1 row)

I can believe older tzdata releases varying from that a little,
but they haven't exactly been adding zone names at a rapid clip.
Either the one you're dealing with is VERY old or it lost some
files sometime.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2024-04-10 20:31:34 Re: Failure of postgres_fdw because of TimeZone setting
Previous Message Adrian Klaver 2024-04-10 20:04:38 Re: Failure of postgres_fdw because of TimeZone setting