Bug 78582 - time zone 'GMT-8' gives weird results
time zone 'GMT-8' gives weird results
Product: Red Hat Linux
Classification: Retired
Component: postgresql (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Andrew Overholt
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2002-11-25 18:49 EST by David Kaplan
Modified: 2007-04-18 12:48 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-03-12 18:44:51 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Kaplan 2002-11-25 18:49:03 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020710

Description of problem:
I generally use PST with no daylight savings for my database - this is Greenwich
Mean Time minus 8 hours.  In order to do this, I would think one would set 


However, this gives the opposite of the desired effect (ie. GMT + 8 hours ).

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
2.SELECT '2002-01-01 00:00-00'::timestamp;

Actual Results:        timestamptz       
 2002-01-01 08:00:00+08
(1 row)

Expected Results:        timestamptz       
 2001-12-31 16:00:00-08
(1 row)

Additional info:

Perhaps this is the way it should be, but seems strange to me.  Also, I am not
sure if this is a problem with the system wide time zone information, or
particular to postgresql.
Comment 1 Andrew Overholt 2003-03-04 12:37:04 EST
Assigning to me.
Comment 2 Andrew Overholt 2003-03-12 18:44:51 EST
tgl@redhat.com says:

you can get the same behavior by doing, eg,
        [tgl@rh1 tgl]$ TZ='GMT' date
        Wed Mar 12 23:23:23 GMT 2003
        [tgl@rh1 tgl]$ TZ='GMT+5' date
        Wed Mar 12 18:23:32 GMT 2003

It's a glibc thing.  Resolving NOTABUG (or at least not a PostgreSQL bug).

Note You need to log in before you can comment on or make changes to this bug.