On Wed, 2012-12-19 at 00:06 +, Peter Geoghegan wrote:
> On 18 December 2012 23:31, Josh Berkus wrote:
> > Jeff, Hackers:
> >
> > Is there a strong reason why this has to error?
>
> Having taken a look at the range I/O routines, I surmise that it was
> just easier to write range_parse() such t
On 18 December 2012 23:31, Josh Berkus wrote:
> Jeff, Hackers:
>
> Is there a strong reason why this has to error?
Having taken a look at the range I/O routines, I surmise that it was
just easier to write range_parse() such that whitespace is included
within tokens:
* Whitespace before or afte
Jeff, Hackers:
Is there a strong reason why this has to error?
postgres=# select '[,]'::TSTZRANGE
postgres-# ;
tstzrange
---
(,)
(1 row)
postgres=# select '[, ]'::TSTZRANGE;
ERROR: invalid input syntax for type timestamp with time zone: " "
LINE 1: select '[, ]'::TSTZRANGE
--Josh
--
liebehenz wrote:
> a_name (char var 48) is sometimes empty in the select of the new 9.2.2
> Version,
>
> the a_name is in the table column set.
>
> Something is going wrong.
> here in screenshot same identical database on 9.2.1 Server and 9.2.2 Server
Character-based results are preferred on a
"liebehenz" writes:
> i have here a strange bug.
Can't really say anything about this without a self-contained test case
(which your screenshot isn't, even if it were 100% readable).
However, are you sure that it's 9.2.2 and not 9.2.1 that's wrong?
There were several planner bugs fixed in betwee
