pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Server Time Setting
6+ messages / 2 participants
[nested] [flat]

* Server Time Setting
@ 2005-09-12 21:05  Lane Van Ingen <lvaningen@esncc.com>
  0 siblings, 2 replies; 6+ messages in thread

From: Lane Van Ingen @ 2005-09-12 21:05 UTC (permalink / raw)
  To: pgsql-admin

I am baffled as to why some of the PostgreSQL functions (like now() ) are
returning
a time which is exactly an hour later than the server's actual system time.

I have checked PostgreSQL config parms by doing a SHOW ALL and search the
manual for
anything else that might be related, yet everything looks fine to me.

Does anybody know why this would be?





^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: Server Time Setting
@ 2005-09-12 21:06  Lane Van Ingen <lvaningen@esncc.com>
  parent: Lane Van Ingen <lvaningen@esncc.com>
  1 sibling, 0 replies; 6+ messages in thread

From: Lane Van Ingen @ 2005-09-12 21:06 UTC (permalink / raw)
  To: pgsql-admin

Forgot to mention, I am using version 8.0.1 on Windows 2003 ...

-----Original Message-----
From: Lane Van Ingen [mailto:lvaningen@esncc.com]
Sent: Monday, September 12, 2005 5:05 PM
To: pgsql-admin@postgresql.org
Subject: Server Time Setting


I am baffled as to why some of the PostgreSQL functions (like now() ) are
returning
a time which is exactly an hour later than the server's actual system time.

I have checked PostgreSQL config parms by doing a SHOW ALL and search the
manual for
anything else that might be related, yet everything looks fine to me.

Does anybody know why this would be?





^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: Server Time Setting
@ 2005-09-12 22:42  Tom Lane <tgl@sss.pgh.pa.us>
  parent: Lane Van Ingen <lvaningen@esncc.com>
  1 sibling, 1 reply; 6+ messages in thread

From: Tom Lane @ 2005-09-12 22:42 UTC (permalink / raw)
  To: Lane Van Ingen <lvaningen@esncc.com>; +Cc: pgsql-admin

"Lane Van Ingen" <lvaningen@esncc.com> writes:
> I am baffled as to why some of the PostgreSQL functions (like now() ) are
> returning
> a time which is exactly an hour later than the server's actual system time.

I'd say you've got TimeZone set to something different than you think
you do.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: Server Time Setting
@ 2005-09-13 14:47  Lane Van Ingen <lvaningen@esncc.com>
  parent: Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 6+ messages in thread

From: Lane Van Ingen @ 2005-09-13 14:47 UTC (permalink / raw)
  To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-admin

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Monday, September 12, 2005 6:42 PM
To: Lane Van Ingen
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Server Time Setting


"Lane Van Ingen" <lvaningen@esncc.com> writes:
>> I am baffled as to why some of the PostgreSQL functions (like now() ) are
>> returning
>> a time which is exactly an hour later than the server's actual system
time.

> I'd say you've got TimeZone set to something different than you think
> you do.
>			regards, tom lane

Before I asked this question yesterday, I had already checked SHOW ALL and
found only
two PostgreSQL config parameters that seemed to apply, and they were set
properly:
  australian_timezones  = no
  TimeZone              = US/Eastern
We are running 8.0.1, Windows 2003.

Since last message, checked 3 other servers, and found that I have the same
problem
on two out of three:
  Server #1: select now() agreed with Windows time on this one
  Server #2: select now() was exactly one hour greater than Windows time
where config
             parms were set the same as previous paragraph
  Server #3: select now() was exactly one hour greater than Windows time,
but config
             parm was set wrong: TimeZone = Europe/Dublin (don't know how
that happened
             but makes you wonder if TimeZone has anything to do with this
at all!)

Windows 2003 time was set correctly in all four cases.

Summary:
  - one server displays time correctly
  - two servers APPEAR to be set correctly, but time displayed from now() as
one hour
    greater than Windows time
  - one server is set incorrectly, but TimeZone did not appear to have any
effect on the
    time being displayed; now() just displayed time as one hour greater than
Windows time

Being as one server is 'doing it right', there must be some difference, but
so far I have
not found what is different.





^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* FW: Server Time Setting
@ 2005-09-14 22:23  Lane Van Ingen <lvaningen@esncc.com>
  0 siblings, 1 reply; 6+ messages in thread

From: Lane Van Ingen @ 2005-09-14 22:23 UTC (permalink / raw)
  To: pgsql-admin

Is there anyone who knows the answer as to why now() is delivering a
different
time answer than Windows?

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Monday, September 12, 2005 6:42 PM
To: Lane Van Ingen
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Server Time Setting

"Lane Van Ingen" <lvaningen@esncc.com> writes:
>> I am baffled as to why some of the PostgreSQL functions (like now() ) are
>> returning a time which is exactly an hour later than the server's actual
>> system time.

> I'd say you've got TimeZone set to something different than you think
> you do.
>			regards, tom lane

Before I asked this question yesterday, I had already checked SHOW ALL and
found only two PostgreSQL config parameters that seemed to apply, and they
appeared to be set properly:
  australian_timezones  = no
  TimeZone              = US/Eastern
We are running 8.0.1, Windows 2003.

Since last message, checked 3 other servers, and found that I have the same
problem on two out of three:
  Server #1: select now() agreed with Windows time on this one
  Server #2: select now() was exactly one hour greater than Windows time
             where config parms were set the same as previous paragraph
  Server #3: select now() was exactly one hour greater than Windows time,
             but config parm was set wrong: TimeZone = Europe/Dublin (don't
             know how that happened; makes you wonder if TimeZone has
             anything to do with this at all!)

Windows 2003 time was set correctly in all four cases.

Summary:
  - one server displays time correctly
  - two servers APPEAR to be set correctly, but time displayed from now() as
    one hour greater than Windows time
  - one server is set incorrectly, but TimeZone did not appear to have any
    effect on the time being displayed; now() just displayed time as one
    hour greater than Windows time

Being as one server is 'doing it right', there must be some difference, but
so far I have not found what is different. Windows appeared to be correct in
all cases, but PostgreSQL did not.

---------------------------(end of broadcast)---------------------------





^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: FW: Server Time Setting
@ 2005-09-15 02:44  Tom Lane <tgl@sss.pgh.pa.us>
  parent: Lane Van Ingen <lvaningen@esncc.com>
  0 siblings, 0 replies; 6+ messages in thread

From: Tom Lane @ 2005-09-15 02:44 UTC (permalink / raw)
  To: Lane Van Ingen <lvaningen@esncc.com>; +Cc: pgsql-admin

"Lane Van Ingen" <lvaningen@esncc.com> writes:
> Is there anyone who knows the answer as to why now() is delivering a
> different time answer than Windows?

pgsql-hackers-win32 might be the place to ask this.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 6+ messages in thread


end of thread, other threads:[~2005-09-15 02:44 UTC | newest]

Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-09-12 21:05 Server Time Setting Lane Van Ingen <lvaningen@esncc.com>
2005-09-12 21:06 ` Lane Van Ingen <lvaningen@esncc.com>
2005-09-12 22:42 ` Tom Lane <tgl@sss.pgh.pa.us>
2005-09-13 14:47   ` Lane Van Ingen <lvaningen@esncc.com>
2005-09-14 22:23 FW: Server Time Setting Lane Van Ingen <lvaningen@esncc.com>
2005-09-15 02:44 ` Tom Lane <tgl@sss.pgh.pa.us>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox