Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tzSSx-002Fb0-39 for pgsql-general@arkaria.postgresql.org; Tue, 01 Apr 2025 03:39:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tzSSu-00FVpY-Vb for pgsql-general@arkaria.postgresql.org; Tue, 01 Apr 2025 03:39:04 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tzSSu-00FVkt-KT for pgsql-general@lists.postgresql.org; Tue, 01 Apr 2025 03:39:04 +0000 Received: from mail-qk1-x732.google.com ([2607:f8b0:4864:20::732]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tzSSt-002GAF-05 for pgsql-general@postgresql.org; Tue, 01 Apr 2025 03:39:03 +0000 Received: by mail-qk1-x732.google.com with SMTP id af79cd13be357-7c559b3eb0bso293409385a.1 for ; Mon, 31 Mar 2025 20:39:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1743478742; x=1744083542; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=TI184fJ5m3VBhYBr2A/nl5+XQcAx/xiziN59d6PE77s=; b=h8XRtGuB4P/ALx5ibbdtfzjiZ3HomydRbSrdBQPQKFEF90KQKrylMRPsNQwG0qsmGA BfiUZwG6c9E2ypI/LQbllzpcpvG8Q4SHom4FRPPGHpj90X17QQGbeiyFzYw7i+Al4o2r xHRKtFJnhVJA/oP0FowK2/OeaPIkA/KJWjiIqU9FKJq3jQi8m6Sw4uljfp/mjU2if6Ag Yv7rfsr3wpECVGrn0Rmyih++0AUcqebXQo4kuS9VzMB0xDFmW0UxtRc93Dnx+HjycqNt qrsSp3MtohqjTpmGcNSZNlsPMsaGK+WodjXWLJiU01F8BgFHNUGTco9ivPlEiST8+0Pw 11fQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1743478742; x=1744083542; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=TI184fJ5m3VBhYBr2A/nl5+XQcAx/xiziN59d6PE77s=; b=D4GbIulqk9Ks+vX5eDtpQNQ3NrYu0AnEYk0yfls7LGQxlCGRTWVLCxrEa2j/SX15ve ApXDLRNcBXCDYfSVY0FbF+e/Ukye8KKft/jq5s91efSyW/Hegr39KngWXZh+WIda9ern fbFVq+vuwmY8KvW+Am74WHirT13DbH4dvWhRBxl3imz9m7VScwWJB9YhYTVQdtRNsjwe 5V5tmzHOI3QCpEVQNQqHIOailneZf/8aYXFhLMv11RPqlie+oSHPdDfjqPFE50gYRKy+ eeMNvbfc2qu9SGnb1RihLbsWnTUmGFt5QADIOX5QaISOlCGlWfNSMhRd8m+lqqwgZLr+ XZCQ== X-Gm-Message-State: AOJu0Yyd7ziBo6GymHftNTojZp61FwL+rOPsm51pii9c4xmJqmrPMhQb dJgg4a27L42vUCGm7pLciSVjhDkeqpusf3WvX8GDeuxkFFkGcOglxoNqoqOKd4L0Y4TgE0Y8DdO 66dTp6CjL8NKH/VzCS1YHg2GHQteptrF6 X-Gm-Gg: ASbGncsIDhXmgqmKoWleHtvRpgyt1j+f9KaKMiMphFFPBNjVW77zVb3o4Kf8erZlX9K Us9XSf44s5NuK0EDP6dtaBLrFvHyIgLn8ajVR+cZRire0cFDYeLGpZ+UE+o+tI2z7SO7hwGiv4u EOWpkSi+Pog1aze8rSg8KVDN+8Mnc= X-Google-Smtp-Source: AGHT+IFl7OxmAOxrTZGYS8TjMeJIUON3bv+ath61n1NkLhCALN8bdaQu6KO8Zf71TMnT5GwLXC3UgDTHnDmXB4ZATRs= X-Received: by 2002:a05:620a:4105:b0:7c5:6ef2:2767 with SMTP id af79cd13be357-7c6862eba77mr1304035385a.2.1743478741066; Mon, 31 Mar 2025 20:39:01 -0700 (PDT) MIME-Version: 1.0 From: Jayadevan M Date: Tue, 1 Apr 2025 09:08:50 +0530 X-Gm-Features: AQ5f1Jp2Rimfih5mWoE2sVsSPQV04mYZfGr5xgSldvS7ySPwwEo-qVOeqJ60rH0 Message-ID: Subject: Doubt on pg_timezone_names and pg_timezone_abbrevs To: "pgsql-general@postgresql.org" Content-Type: multipart/alternative; boundary="00000000000008f1b00631af47c7" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000008f1b00631af47c7 Content-Type: text/plain; charset="UTF-8" Hello PG members, I used 'IST' in a query like this - * (timestamp_hour) at time zone 'IST' time_ist *and did not get the expected output - timestamp in Indian Standard Time. So I queried the 2 views that provide timezone info and did not really understand the abbrev column. select name, abbrev, utc_offset from pg_timezone_names where abbrev = 'IST' ; name | abbrev | utc_offset ---------------+--------+------------ Eire | IST | 01:00:00 Asia/Kolkata | IST | 05:30:00 Asia/Calcutta | IST | 05:30:00 Europe/Dublin | IST | 01:00:00 select * from pg_timezone_abbrevs where abbrev = 'IST' ; abbrev | utc_offset | is_dst --------+------------+-------- IST | 02:00:00 | f This is PostgreSQL 13.15 on AWS RDS. We have the same abbrev for 4 timezones in pg_timezone_names. Regards, Jayadevan --00000000000008f1b00631af47c7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello PG members,
I used 'IST'=C2=A0 in a quer= y like this -=C2=A0=C2=A0(timestamp_hour) at time zone 'IST' = time_ist and did not get the expected output - timestamp in Indian = Standard Time. So I queried the 2 views that provide timezone info and did = not really understand the abbrev column.=C2=A0
select name, abbre= v, utc_offset =C2=A0from pg_timezone_names =C2=A0where abbrev =3D 'IST&= #39; =C2=A0;
=C2=A0 =C2=A0 =C2=A0name =C2=A0 =C2=A0 =C2=A0| abbrev | utc= _offset
---------------+--------+------------
=C2=A0Eire =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0| IST =C2=A0 =C2=A0| 01:00:00
=C2=A0Asia/Kolkata= =C2=A0| IST =C2=A0 =C2=A0| 05:30:00
=C2=A0Asia/Calcutta | IST =C2=A0 = =C2=A0| 05:30:00
=C2=A0Europe/Dublin | IST =C2=A0 =C2=A0| 01:00:00

select * from pg_timezone_abbrevs where abbrev =3D 'IST' =C2= =A0;
=C2=A0abbrev | utc_offset | is_dst
--------+------------+------= --
=C2=A0IST =C2=A0 =C2=A0| 02:00:00 =C2=A0 | f

This is=C2=A0PostgreSQL 13.15 on AWS RDS. We have the same abbrev for 4 ti= mezones in pg_timezone_names.
Regards,
Jayadevan
<= div>


--00000000000008f1b00631af47c7--