| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Louis-David Mitterrand <vindex+lists-pgsql-general(at)apartia(dot)org> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: timestamp skew during 7.4 -> 8.2 upgrade |
| Date: | 2007-08-11 15:58:03 |
| Message-ID: | 2154.1186847883@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Louis-David Mitterrand <vindex+lists-pgsql-general(at)apartia(dot)org> writes:
> But, I found something fishy that particular server:
> uruk:~# hwclock
> Sat 11 Aug 2007 10:47:36 AM CEST -0.630123 seconds
> uruk:~# hwclock --utc
> Sat 11 Aug 2007 12:47:39 PM CEST -0.600430 seconds
If this is PC-type hardware, I'd guess that something is confused about
whether the hardware clock is running in UTC or local time.
> Is postgres using the same time reference as "hwclock" or "date" ?
I'd expect PG to get the same results as "date". I have no idea what
"hwclock" is really doing.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2007-08-11 16:10:04 | Re: Trigger Procedure Error: NEW used in query that is not in a rule |
| Previous Message | Tom Lane | 2007-08-11 15:50:41 | Re: Trigger Procedure Error: NEW used in query that is not in a rule |