Re: BUG #14300: Empty cube representation

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: a(at)ustimen(dot)co
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14300: Empty cube representation
Date: 2016-08-29 16:24:43
Message-ID: 9274.1472487883@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

a(at)ustimen(dot)co writes:
> SELECT CUBE(ARRAY[]::INTEGER[]);
> -- Gives '()'
> SELECT '()'::CUBE;
> -- Gives 'ERROR: bad cube representation'

Hmm. There are more ways than that to produce a cube that cube_in won't
take: you can put in an infinity or NaN coordinate via the cube-from-
float-array path too, and cube_out will print them, but cube_in won't
take them. We fixed something similar with the core geometric types
recently.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Spencer Thomason 2016-08-29 17:32:02 Re: BUG #14295: Hot standby crash during tsvector rebuild
Previous Message Tom Lane 2016-08-29 15:28:34 Re: BUG #14301: function in case expression called when it should not be