Thu Jul 5 13:55:21 PDT 2007
- Previous message: [Slony1-general] timestamp with time zone insanity
- Next message: [Slony1-general] Soliciting ideas for v2.0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Jul 02, 2007 at 10:54:35PM -0400, Bill Moran wrote: > On both systems, the database is set to est5edt timezone, yet some > rows (not all, mind you) change the timezone from edt to est when > the data is replicated. Just as a point of information, since I see you have the problem fixed, this can _never_ be true in the sense of changing the data. PostgreSQL stores its dates internally as UTC, so if your client timezone setting changes, you'll see a difference. So whenever you see something like this, look for a problem around how the data is being presented (like in your case, different timezone rules). A -- Andrew Sullivan | ajs at crankycanuck.ca The very definition of "news" is "something that hardly ever happens." --Bruce Schneier
- Previous message: [Slony1-general] timestamp with time zone insanity
- Next message: [Slony1-general] Soliciting ideas for v2.0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list