Re: BUG #13687: bug in row_to_json function with '-infinity' timestamp

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, stepanperlov(at)gmail(dot)com, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13687: bug in row_to_json function with '-infinity' timestamp
Date: 2015-10-19 16:54:31
Message-ID: 1256.1445273671@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> ... But since ISO 8601 doesn't define infinity our implementation of this
> behavior is not externally constrained and probably shouldn't be changed.

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.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2015-10-19 18:01:41 Re: BUG #13687: bug in row_to_json function with '-infinity' timestamp
Previous Message Tom Lane 2015-10-19 16:44:55 pg_regprefix() doesn't handle lookahead constraints correctly