public inbox for [email protected]  
help / color / mirror / Atom feed
Re: Failure of postgres_fdw because of TimeZone setting
2+ messages / 2 participants
[nested] [flat]

* Re: Failure of postgres_fdw because of TimeZone setting
@ 2024-04-10 20:31 Tom Lane <[email protected]>
  2024-04-10 21:25 ` Re: Failure of postgres_fdw because of TimeZone setting Adrian Klaver <[email protected]>
  0 siblings, 1 reply; 2+ messages in thread

From: Tom Lane @ 2024-04-10 20:31 UTC (permalink / raw)
  To: Adrian Klaver <[email protected]>; +Cc: Adnan Dautovic <[email protected]>; pgsql-general

Adrian Klaver <[email protected]> writes:
> On 4/10/24 12:38, Adnan Dautovic wrote:
>> 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.

> On my instance of Postgres 16.2, 1196.

You're probably using a build with --with-system-tzdata pointing
at a system tzdata tree that includes leap-second-aware zones.
These tend to have duplicative entries like "America/New_York"
and "posix/America/New_York".  (There's also a subtree like
"right/America/New_York", but we reject those because we don't
do leap seconds.)  The real number of distinct zones in a
standard tzdata file set these days is a shade under 600.

			regards, tom lane






^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: Failure of postgres_fdw because of TimeZone setting
  2024-04-10 20:31 Re: Failure of postgres_fdw because of TimeZone setting Tom Lane <[email protected]>
@ 2024-04-10 21:25 ` Adrian Klaver <[email protected]>
  0 siblings, 0 replies; 2+ messages in thread

From: Adrian Klaver @ 2024-04-10 21:25 UTC (permalink / raw)
  To: Tom Lane <[email protected]>; +Cc: Adnan Dautovic <[email protected]>; pgsql-general



On 4/10/24 1:31 PM, Tom Lane wrote:
> Adrian Klaver <[email protected]> writes:
>> On 4/10/24 12:38, Adnan Dautovic wrote:
>>> 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.
> 
>> On my instance of Postgres 16.2, 1196.
> 
> You're probably using a build with --with-system-tzdata pointing
> at a system tzdata tree that includes leap-second-aware zones.
> These tend to have duplicative entries like "America/New_York"
> and "posix/America/New_York".  (There's also a subtree like
> "right/America/New_York", but we reject those because we don't
> do leap seconds.)  The real number of distinct zones in a
> standard tzdata file set these days is a shade under 600.

It's the PGDG package running on Ubuntu 22.04.

> 
> 			regards, tom lane

-- 
Adrian Klaver
[email protected]






^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2024-04-10 21:25 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-04-10 20:31 Re: Failure of postgres_fdw because of TimeZone setting Tom Lane <[email protected]>
2024-04-10 21:25 ` Adrian Klaver <[email protected]>

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox