On Thu, Mar 03, 2011 at 09:27:58PM +0200, Heikki Linnakangas wrote:
> Yes, we use David Olson's tz database. According to this proposal, David
> Olson is retiring, and they propose that IETF takes over maintainership
> of the tz database.
Yeah, I guess I ought to have summarized. That is inde
On 03.03.2011 20:45, Andrew Sullivan wrote:
Today on the ietf-applications list, I saw this:
http://www.ietf.org/mail-archive/web/apps-discuss/current/msg02301.html
If there are particular issues with respect to the time zone database
stuff that you all have struggled with and want highlighted,
Hackers,
Today on the ietf-applications list, I saw this:
http://www.ietf.org/mail-archive/web/apps-discuss/current/msg02301.html
If there are particular issues with respect to the time zone database
stuff that you all have struggled with and want highlighted, feel free
to send them to me and I'
Joachim Wieland writes:
> this is a reply to the following post:
> http://archives.postgresql.org/message-id/7867.1219793...@sss.pgh.pa.us
> which is also a TODO item:
> [E] Revise the src/timezone/tznames abbreviation files:
> * to add missing abbreviations
> * to find abbreviations tha
Hi all,
this is a reply to the following post:
http://archives.postgresql.org/message-id/7867.1219793...@sss.pgh.pa.us
which is also a TODO item:
[E] Incomplete itemRevise the src/timezone/tznames abbreviation files:
* to add missing abbreviations
* to find abbreviations that can be sa
On Sun, 20 Feb 2005, Tom Lane wrote:
Hmm, all of those should work (and do work here). Are the corresponding
files present in the appropriate installation directory? Look under
.../share/postgresql/timezone/
They are not; it's evidently a problem with the way the NetBSD package
installs things. I
Curt Sampson <[EMAIL PROTECTED]> writes:
> I'm running PostgreSQL 8.0.1 from the NetBSD pkgsrc package. I'm getting some
> odd behavior with time zone names:
> SET timezone TO 'EST';
> psql:z.sql:2: ERROR: unrecognized time zone name: "EST"
> SET timezone TO 'Asia/Tokyo';
> ps
I'm running PostgreSQL 8.0.1 from the NetBSD pkgsrc package. I'm getting some
odd behavior with time zone names:
SET timezone TO 'JST';
psql:z.sql:1: ERROR: unrecognized time zone name: "JST"
SET timezone TO 'EST';
psql:z.sql:2: ERROR: unrecognized time zone name: "EST"
SET ti
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> Hi, it seems there is an inconsistency with time zone handling to me:
Yeah, the set of time zone names accepted by SET TIME ZONE doesn't have
a whole lot to do with the set of time zone names you can specify as
part of a timestamptz input string.
This is
Hi, it seems there is an inconsistency with time zone handling to me:
test=# select version();
version
-
PostgreSQL 7.4 on i686-pc-linux-gnu, compiled by GCC 2.95.3
(1 row)
test=# se
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Considering the time zone abbreviations that are accepted on input, I find
> a couple of bogosities:
Presumably we can get some local knowledge on those items from list
members. I believe that Thomas created the TZ tables on the basis of
including ev
Considering the time zone abbreviations that are accepted on input, I find
a couple of bogosities:
WDT +09:00 West Australian Daylight Time
AWST+08:00 Australia Western Standard Time
WADT+08:00 West Australian Daylight Time
WST +08:00 West Australian Standard Time
WAST+07:0
> australia=# select '2002-03-18 00:00:00' at time zone 'Australia/Sydney';
> ERROR: Time zone 'australia/sydney' not recognized
> australia=# set time zone 'Australia/Sydney';
> SET VARIABLE
> australia=# select '2002-03-18 00:00:00';
> ?column?
> -
> 2002-03-18 00:00:
I need to do some timezone manipulation, and I was wondering about this
difference:
australia=# select version();
version
--
PostgreSQL 7.1.3 on i386--freebsd4.4, compiled by GCC 2.95.3
(1 row)
australia=# sel
14 matches
Mail list logo