From: | Együd Csaba <csegyud(at)vnet(dot)hu> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Best practices: Handling Daylight-saving time |
Date: | 2005-03-11 14:25:28 |
Message-ID: | 0ID6006FVYQFZX@mail.vnet.hu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi All,
I'd like to ask your opininon about how to handle DST on an 7/24 system.
Where should it be handled: on the server side or on the client side? And
how could I (at all could I???) make it transparent?
Or we must bow to the fact that twice a year there are two unusable hours?
If it cannot be solved technically, than it is acceptable, but if there is a
chance to do it, I'd like to try it.
Our system stores 200-1000 measured data per minute, comming from
substations. The substations clock is synchronized periodically as well.
When the DST is switched there is 1 hour of data missing (or overlapped).
Certainly the client machines are autmatically adjusted for the DST.
How do this others?
Many many thanks,
-- Csaba
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.6.4 - Release Date: 2005.03.07.
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.6.4 - Release Date: 2005.03.07.
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Browne | 2005-03-11 14:40:13 | Re: PostgreSQL still for Linux only? |
Previous Message | Alvaro Herrera | 2005-03-11 14:23:51 | Re: Problem with inherited table, can you help?... |