From: Tom Lane <tgl@sss.pgh.pa.us>
To: gkchinna.oracle@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18455: DST information is flagged wrongly
In-reply-to: <18455-1f7c5337666bbd1a@postgresql.org>
References: <18455-1f7c5337666bbd1a@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Thu, 02 May 2024 12:21:24 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2219449.1714662503.1@sss.pgh.pa.us>
Date: Thu, 02 May 2024 11:08:23 -0400
Message-ID: <2219450.1714662503@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2219450.1714662503%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> postgres=# select * from pg_timezone_names where name ilike '%dublin%';
>      name      | abbrev | utc_offset | is_dst 
> ---------------+--------+------------+--------
>  Europe/Dublin | IST    | 01:00:00   | f
> (1 row)

Huh, that is very interesting.  On my MacBook with a
build using --with-system-tzdata=/usr/share/zoneinfo,
I get:

postgres=# select * from pg_timezone_names where name ilike '%dublin%';
     name      | abbrev | utc_offset | is_dst 
---------------+--------+------------+--------
 Europe/Dublin | IST    | 01:00:00   | t
(1 row)

and the same on a RHEL box.  However, if I build using
PG's internal copy of the timezone database:

regression=# select * from pg_timezone_names where name ilike '%dublin%';
     name      | abbrev | utc_offset | is_dst 
---------------+--------+------------+--------
 Europe/Dublin | IST    | 01:00:00   | f
(1 row)

We're all on 2024a (and Europe/Dublin hasn't changed definition
recently anyway), so what's going on there?

I suspect this may be down to different options being used in
the "zic" run that builds the zone data files, but haven't
had time to look closer than that.

			regards, tom lane