Re: Should we throw error when converting a nonexistent/ambiguous timestamp? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Should we throw error when converting a nonexistent/ambiguous timestamp?
Date
Msg-id 27506.1268703446@sss.pgh.pa.us
Whole thread Raw
In response to Re: Should we throw error when converting a nonexistent/ambiguous timestamp?  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Mon, Mar 15, 2010 at 9:12 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> The current code behavior seems to me to be on par with, for example,
>> trying to intuit MM-DD versus DD-MM field orders. �We used to try to
>> do that, too, and gave it up as a bad idea.

> I suppose it's topologically equivalent, but to me that is an order of
> magnitude crazier than this case.

> Of course I may be in the minority...  but you did ask...

Well, the purpose of asking is to see whether there's a consensus for
doing something.  If not, fine, it's one less thing to worry about...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: walreceiver is uninterruptible on win32
Next
From: Greg Smith
Date:
Subject: Re: Ragged latency log data in multi-threaded pgbench