Re: Bug#311533: Invalid timestamp returned because of timezone

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Martin Pitt <martin(at)piware(dot)de>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Bug#311533: Invalid timestamp returned because of timezone
Date: 2005-06-13 14:25:01
Message-ID: 19550.1118672701@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Martin Pitt <martin(at)piware(dot)de> writes:
> I just thought about how to provide a transition path if the long-term
> solution really was to get rid of integer time stamps.

I don't think anyone has suggested doing that. In fact, there's a camp
that wishes they'd become the default. I don't see that happening soon
either, in part because it seems there are still too many bugs to be
flushed out :-(. But *somebody* has to exercise the code in order to
flush out the bugs, and Debian has elected to be the pioneers here.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message James Doherty 2005-06-13 15:28:00 Re: BUG #1715: dbmirror replaces nextval, setval functions
Previous Message Mauro Delfino 2005-06-13 13:12:38 Re: BUG #1698: Different behavior in UNIQUE and DISTINCT