Skip site navigation (1) Skip section navigation (2)

Re: Australian timezone configure option

From: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>
To: chris(dot)bitmead(at)health(dot)gov(dot)au
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, Chris Dunlop <chris(at)onthe(dot)net(dot)au>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Australian timezone configure option
Date: 2001-06-14 00:23:22
Message-ID: 3B2803FA.65F5C518@alumni.caltech.edu (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
> Surely the correct solution is to have a config file somewhere
> that gets read on startup? That way us Australians don't have to be the only
> ones in the world that need a custom built postgres.

I will point out that "you Australians", and, well, "us 'mericans", are
the only countries without the sense to choose unique conventions for
time zone names.

It sounds like having a second lookup table for the Australian rules is
a possibility, and this sounds fairly reasonable to me. Btw, is there an
Australian convention for referring to North American time zones for
those zones with naming conflicts?

                       - Thomas

In response to

Responses

pgsql-hackers by date

Next:From: Thomas LockhartDate: 2001-06-14 00:29:18
Subject: Re: Australian timezone configure option
Previous:From: Bruce MomjianDate: 2001-06-13 22:44:53
Subject: Re: [PATCH] addition of text_inet, text_cidr and inet_set_masklen

pgsql-patches by date

Next:From: Thomas LockhartDate: 2001-06-14 00:29:18
Subject: Re: Australian timezone configure option
Previous:From: Rainer MagerDate: 2001-06-13 22:37:57
Subject: High memory usage

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group