Re: Failure of postgres_fdw because of TimeZone setting

Hi,

On 05. Apr 2024, at 16:13, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>Adnan Dautovic <daut(at)mailbox(dot)org> writes:
>> SELECT * FROM pg_timezone_names ORDER BY name;
>
>>> "name" "abbrev" "utc_offset" "is_dst"
>>> "Turkey" "+03" "03:00:00" false
>>> "UCT" "UCT" "00:00:00" false
>>> "Universal" "UTC" "00:00:00" false
>>> "W-SU" "MSK" "03:00:00" false
>
>Wow. To clarify, is that the *whole* result?

I apologize for the confusion, this is an excerpt where I cut out
everything before "Turkey" and after "W-SU". Between those, the
output is complete.

>Out of curiosity, does
> SET timezone to 'GMT';
>work?

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

The corresponding excerpt from pg_timezone_names is:
>"name" "abbrev" "utc_offset" "is_dst"
> [snip]
>"Europe/Zurich" "CEST" "02:00:00" true
>"GB-Eire" "BST" "01:00:00" true
>"Greenwich" "GMT" "00:00:00" false
>"HST" "HST" "-10:00:00" false
>"Hongkong" "HKT" "08:00:00" false
>"Iceland" "GMT" "00:00:00" false
> [snip]

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.

Kind regards,

Adnan Dautovic