If it's known that slon has problems with time zones with daylight savings time, wouldn't it make sense to default it to UTC or at least give you a warning when it starts up?   I had no idea about this and I could see others being bit in the rump by this as well.  I've set up my scripts to use TZ=UTC now instead of the machines local time zone and have restarted them, but now I wonder what would have happened if I didn't read this thread?

That being said wouldn't it make more sense, like the OP is saying, to  use timestamp without timezone?   Why give someone a gun to shoot themselves in the foot if it can be avoided?

--brian

On Nov 1, 2010, at 9:53 AM, Christopher Browne wrote:

> Ger Timmens <Ger.Timmens at adyen.com> writes:
>> I understand, but maybe I wasn't clear:
>> The column defition of the slony sl_ tables should be adapted
>> to 'timestamp with time zone' instead of 'timestamp without
>> timezone' to prevent any errors in monitoring scripts when
>> the clock goes one hour back from summer to winter time.
>> 
>> So it's more of a suggestion/patch for
>> slony-1.2.22 and slony-2.0.6.
> 
> Ah.
> 
> If the slon processes are running in UTC/GMT, as is recommended, then
> there's no issue whatever, because UTC/GMT do not adjust for DST.
> 
> <http://www.slony.info/adminguide/slony1-1.2.6/doc/adminguide/requirements.html#TIMES>
> -- 
> let name="cbbrowne" and tld="ca.afilias.info" in String.concat "@" [name;tld];;
> Christopher Browne
> "Bother,"  said Pooh,  "Eeyore, ready  two photon  torpedoes  and lock
> phasers on the Heffalump, Piglet, meet me in transporter room three"
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general