http://www.slony.info/bugzilla/show_bug.cgi?id=163

           Summary: Resolve Timezone ambiguity
           Product: Slony-I
           Version: devel
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: low
         Component: slon
        AssignedTo: slony1-bugs at lists.slony.info
        ReportedBy: cbbrowne at ca.afilias.info
                CC: slony1-bugs at lists.slony.info
   Estimated Hours: 0.0


There is a concern out there as to what happens if Slony-I is operating in a
timezone that has the Daylight Savings Time discontinuity.

Some ways of addressing this include:

a) Changing Slony-I tables that have TIMESTAMP values to, instead, have
TIMESTAMP WITH TIMEZONE.

Downsides include that this involves a number of alterations to existing
tables, with a conversion ambiguity.  (e.g. - what should be done with existing
data?  This seems notably risky if the existing timestamps surround the
discontinuity.)

b) Have the slon "health check" (see bug #156) look at the timezone in
TimeZone, and warn if it has a discontinuity.

Open question:  UTC and GMT would be acceptable timezones; what others are
potentially acceptable?

c) Have slon process expressly use UTC as its timezone.

This might change logging output, and be unpopular to users accustomed to
operating Slony in some other timezone.

-- 
Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.