Re: Time Zone in Postgres

[Shilpa Sudhakar <ssudhakar(at)internode(dot)com(dot)au>]

Hi Cat,

As per my previous mail, i've done few checks on the postgres timezone 
files but not sure if am looking at the right file.

I'll paste the details again below .

1) Checked the *postgresql.conf file* and the *timezone *parameter is 
set as "*unknown*".

2) 
*/local/pkgsrc/databases/postgresql80-pgcrypto/work/postgresql-8.0.9/src/timezone/data 
$ grep 2007 australasia*
Rule    AS      2007    max     -       Mar     lastSun 2:00s   0       -
Rule    AT      2007    max     -       Mar     lastSun 2:00s   0       -
Rule    AV      2007    max     -       Mar     lastSun 2:00s   0       -
Rule    AN      2007    max     -       Mar     lastSun 2:00s   0       -
Rule    LH      2007    max     -       Mar     lastSun 2:00    0       -

*/local/pkgsrc/databases/postgresql80-pgcrypto/work/postgresql-8.0.9/src/timezone/data 
$ grep 2008 australasia*

No results

From 2008, the DST ends on first Sunday of April and not on the last 
Sun of March.

Thanks



cat(at)zip(dot)com(dot)au wrote:
> On Fri, Mar 07, 2008 at 09:26:51AM +1030, Shilpa Sudhakar wrote:
>   
> > Hi Tom,
> >
> > We have different databases with different versions.
> >
> > I checked the database with *version 8.2.4* by running the below query
> >
> > echo select timestamp with time zone \'epoch\' + 1206970200 \* INTERVAL 
> > \'1 second\'\; | psql template1
> >         ?column?
> > ---------------------------
> > 2008-03-31 23:00:00+09:30
> > (1 row)
> >
> > This shows the wrong date. The actual result should be  *2008-04-01 
> > 00:00:00+10:30 *
> >     
>
> I believe postgres comes with its own timezone info. Check if the stuff
> it has has the right timezone information. Personally I get it to use
> the system timezone definitions so that I can keep things upto-date
> easier.
>
>