From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Brandon Aiken" <BAiken(at)winemantech(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Anyone using "POSIX" time zone offset capability? |
Date: | 2006-10-16 23:16:29 |
Message-ID: | 7168.1161040589@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
"Brandon Aiken" <BAiken(at)winemantech(dot)com> writes:
> What about time zones like Tehran (GMT+3:30), Kabul (GMT+4:30), Katmandu
> (GMT+5:45) and other non-cardinal-hour GMT offsets? Is this handled in
> some *documented* way already?
Sure. This has worked since PG 7.2 or so:
regression=# select '12:34:00 IRT'::timetz;
timetz
----------------
12:34:00+03:30
(1 row)
Also you can just do
regression=# select '12:34:00 +03:30'::timetz;
timetz
----------------
12:34:00+03:30
(1 row)
regression=#
The weird thing about this allegedly-POSIX notation is the combination
of a symbolic name and a further offset from it. Back when we didn't
have customizable timezone abbreviations, maybe there would be some
point in making that work, but I don't see the point now. I'm not
entirely convinced that it really is a POSIX-sanctioned notation,
either --- the POSIX syntax the zic code knows about is different.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-10-16 23:38:08 | Re: RES: RES: Dates rejected |
Previous Message | Brandon Aiken | 2006-10-16 22:29:04 | Re: Anyone using "POSIX" time zone offset capability? |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeremy Drake | 2006-10-16 23:46:02 | Re: Postgresql Caching |
Previous Message | Brandon Aiken | 2006-10-16 22:29:04 | Re: Anyone using "POSIX" time zone offset capability? |