Re: BUG #13687: bug in row_to_json function with '-infinity' timestamp - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #13687: bug in row_to_json function with '-infinity' timestamp
Date
Msg-id CAKFQuwYo5PFbpZ2AZwY2EzePp6RcNqBTMfr4eD-CBaFcxbp13w@mail.gmail.com
Whole thread Raw
In response to Re: BUG #13687: bug in row_to_json function with '-infinity' timestamp  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Mon, Oct 19, 2015 at 12:54 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> "David G. Johnston" <david.g.johnston@gmail.com> writes:
> > ... =E2=80=8BBut since ISO 8601 doesn't define infinity our implementat=
ion of
> this
> > behavior is not externally constrained and probably shouldn't be change=
d.
>
> But we already did change it, ie, 9.4 is failing to follow the precedent
> established by 9.2 and 9.3.  And that was not an intentional thing, nor
> is it more reasonable than the previous behavior, so I think it's a bug.
>

=E2=80=8BThat was what I was getting it.  It shouldn't be changed from the =
prior
behavior.  Clarified under Bruce's response pointing out the same...

David J.

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #13687: bug in row_to_json function with '-infinity' timestamp
Next
From: Tom Lane
Date:
Subject: Re: BUG #13687: bug in row_to_json function with '-infinity' timestamp