Re: The contents of the pg_timezone_names view bring some surprises

On 2021-05-23 12:55:52 -0700, Bryn Llewellyn wrote: > But it doesn't necessarily error when presented with a key that it > doesn't have. This, too, has been discussed at length in this > exchanges. These examples make the point. > > set timezone = 'UTC'; > select '2021-05-23 19:00:00 foo42bar'::ti

Re: The contents of the pg_timezone_names view bring some surprises

> t...@sss.pgh.pa.us wrote: > >> adrian.kla...@aklaver.com wote: >> >>> Bryn wrote: >>> >>> (1) In the context of discussing timezones, the English word "abbreviation" >>> maps to two distinct notions in PG: "pg_timezone_names.abbre

Re: The contents of the pg_timezone_names view bring some surprises

Adrian Klaver writes: > On 5/22/21 5:52 PM, Bryn Llewellyn wrote: >> (1) In the context of discussing timezones, the English word >> "abbreviation" maps to two distinct notions in PG: >> "pg_timezone_names.abbrev"; and "pg_timezone_abbrevs.abbrev". Tom >> earlier said « there are two views [bec

Re: The contents of the pg_timezone_names view bring some surprises

On 5/22/21 5:52 PM, Bryn Llewellyn wrote: Tom, David, Adrian, and Peter—thank you all very much for taking an interest in my questions. Your responses have, collectively, been an enormous help. I deleted the text of the exchanges in this particular branch of the overall discussion because it's

Re: The contents of the pg_timezone_names view bring some surprises

Tom, David, Adrian, and Peter—thank you all very much for taking an interest in my questions. Your responses have, collectively, been an enormous help. I deleted the text of the exchanges in this particular branch of the overall discussion because it's become rather difficult to work out who sai

Re: The contents of the pg_timezone_names view bring some surprises

On 5/22/21 10:55 AM, Peter J. Holzer wrote: On 2021-05-22 08:26:27 -0700, Adrian Klaver wrote: On 5/22/21 3:09 AM, Peter J. Holzer wrote: On 2021-05-19 06:57:13 -0700, Adrian Klaver wrote: On 5/18/21 11:31 PM, Bryn Llewellyn wrote: This claims (as I read it) that a time zone abbreviation uniq

Re: The contents of the pg_timezone_names view bring some surprises

On 2021-05-22 08:26:27 -0700, Adrian Klaver wrote: > On 5/22/21 3:09 AM, Peter J. Holzer wrote: > > On 2021-05-19 06:57:13 -0700, Adrian Klaver wrote: > > > On 5/18/21 11:31 PM, Bryn Llewellyn wrote: > > > > This claims (as I read it) that a time zone abbreviation uniquely > > > > determines an off

Re: The contents of the pg_timezone_names view bring some surprises

On 5/22/21 3:09 AM, Peter J. Holzer wrote: On 2021-05-19 06:57:13 -0700, Adrian Klaver wrote: On 5/18/21 11:31 PM, Bryn Llewellyn wrote: This seems to be at odds with what section “8.5.3. Time Zones” at https://www.postgresql.org/docs/current/datatype-datetime.html#DATATYPE-TIMEZONES

Re: The contents of the pg_timezone_names view bring some surprises

On 2021-05-22 12:09:23 +0200, Peter J. Holzer wrote: > On 2021-05-19 06:57:13 -0700, Adrian Klaver wrote: > > On 5/18/21 11:31 PM, Bryn Llewellyn wrote: > > > This seems to be at odds with what section “8.5.3. Time Zones” at > > > > > > https://www.postgresql.org/docs/current/datatype-datetime.htm

Re: The contents of the pg_timezone_names view bring some surprises

On 2021-05-19 06:57:13 -0700, Adrian Klaver wrote: > On 5/18/21 11:31 PM, Bryn Llewellyn wrote: > > This seems to be at odds with what section “8.5.3. Time Zones” at > > > > https://www.postgresql.org/docs/current/datatype-datetime.html#DATATYPE-TIMEZONES > > > >

Re: The contents of the pg_timezone_names view bring some surprises

On 2021-05-18 23:31:57 -0700, Bryn Llewellyn wrote: > Africa/Algiers | CET| 01:00:00 | f > Africa/Cairo | EET| 02:00:00 | f > Africa/Tripoli | EET| 02:00:00 | f > Africa/Tunis | CET| 01:00:00 | f > CET| CEST | 02:00:00 | t > EET

Re: The contents of the pg_timezone_names view bring some surprises

On 5/19/21 5:50 PM, Bryn Llewellyn wrote: Thanks, as ever, David and Tom, for your quick responses. Thanks also to Adrian Klaver, who replied in a branched thread with this—in response to my comment about my reading of the information content of the pg_timezone_abbrevs view: « This claims (as

Re: The contents of the pg_timezone_names view bring some surprises

> t...@sss.pgh.pa.us wrote: > >> david.g.johns...@gmail.com wrote: >> >>> b...@yugabyte.com wrote: >>> >>> Am I missing an essential clue to resolving what seems to me to be a >>> paradox? Or am I seeing two kinds of bug? >> >> >> You are missing the materi

Re: The contents of the pg_timezone_names view bring some surprises

On 5/18/21 11:31 PM, Bryn Llewellyn wrote: Some time zones have abbreviations that are identical to their names. This query: Here’s what seems to me to be a closely related dilemma. I’d thought that an abbrev uniquely specified the utc_offset. But this test shows that it doesn’t: with   v1

Re: The contents of the pg_timezone_names view bring some surprises

"David G. Johnston" writes: > On Tuesday, May 18, 2021, Bryn Llewellyn wrote: >> Am I missing an essential clue to resolving what seems to me to be a >> paradox? Or am I seeing two kinds of bug? > You are missing the material in appendix B.4 > https://www.postgresql.org/docs/current/datetime-con

Re: The contents of the pg_timezone_names view bring some surprises

On Tuesday, May 18, 2021, Bryn Llewellyn wrote: > Some time zones have abbreviations that are identical to their names. This > query: > > Am I missing an essential clue to resolving what seems to me to be a > paradox? Or am I seeing two kinds of bug? > > You are missing the material in appendix B

The contents of the pg_timezone_names view bring some surprises

Some time zones have abbreviations that are identical to their names. This query: select name from pg_timezone_names where abbrev = name order by name; gets this result: EST GMT HST MST UCT UTC This, in itself, doesn’t seem remarkable. I wondered if any time zones have names that occur as tim