Re: Failure of postgres_fdw because of TimeZone setting - Mailing list pgsql-general

From Tom Lane
Subject Re: Failure of postgres_fdw because of TimeZone setting
Date
Msg-id 4170840.1712780507@sss.pgh.pa.us
Whole thread Raw
In response to Re: Failure of postgres_fdw because of TimeZone setting  (Adnan Dautovic <daut@mailbox.org>)
List pgsql-general
Adnan Dautovic <daut@mailbox.org> writes:
> On 05. Apr 2024, at 16:13, Tom Lane <tgl@sss.pgh.pa.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



pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Failure of postgres_fdw because of TimeZone setting
Next
From: Tom Lane
Date:
Subject: Re: Failure of postgres_fdw because of TimeZone setting