Re: BUG #9227: Error on SELECT ROW OVERLAPS ROW with single ROW argument - Mailing list pgsql-bugs

From Joshua Yanovski
Subject Re: BUG #9227: Error on SELECT ROW OVERLAPS ROW with single ROW argument
Date
Msg-id CABz-M-FHpYoJ+s+t5ktAu9e8y57PnU3zBGakNe3GtHxnOtAcGA@mail.gmail.com
Whole thread Raw
In response to BUG #9227: Error on SELECT ROW OVERLAPS ROW with single ROW argument  (pythonesque@gmail.com)
List pgsql-bugs
This becomes clearer when I perform this in a PREPARE:

# PREPARE foo AS SELECT ROW(1) OVERLAPS ROW(2);
ERROR:  54001: stack depth limit exceeded
HINT:  Increase the configuration parameter "max_stack_depth"
(currently 2048kB), after ensuring the platform's stack depth limit is
adequate.
LOCATION:  check_stack_depth, postgres.c:3090

On Fri, Feb 14, 2014 at 7:55 PM,  <pythonesque@gmail.com> wrote:
> The following bug has been logged on the website:
>
> Bug reference:      9227
> Logged by:          Joshua Yanovski
> Email address:      pythonesque@gmail.com
> PostgreSQL version: 9.3.2
> Operating system:   Ubuntu 12.0.4
> Description:
>
> # SELECT ROW (1) OVERLAPS ROW (2);
> ERROR:  XX000: unrecognized node type: 656
> LOCATION:  transformExprRecurse, parse_expr.c:359
>
> I'm not sure why this even parses, as it's not documented to do so.  I do
> notice, however, that in makeOverlaps in gram.y creates a recursive list
> when largs or args has only one argument, which seems wrong to me.
>
>
>



--
Josh

pgsql-bugs by date:

Previous
From: Pierre
Date:
Subject: No optimization with a partition window in a view
Next
From: Jeff Janes
Date:
Subject: Re: BUG #9161: wal_writer_delay is limited to 10s