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-FwbWJ06QCER+-oJLyQz9JW7jXY3PcwF3HdGi5W751P1w@mail.gmail.com
Whole thread Raw
In response to Re: BUG #9227: Error on SELECT ROW OVERLAPS ROW with single ROW argument  (Joshua Yanovski <pythonesque@gmail.com>)
Responses Re: BUG #9227: Error on SELECT ROW OVERLAPS ROW with single ROW argument
List pgsql-bugs
Sorry, the MIME type seems to have gotten screwed up, hopefully this
will work better.

On Mon, Feb 17, 2014 at 9:33 PM, Joshua Yanovski <pythonesque@gmail.com> wrote:
> On Mon, Feb 17, 2014 at 5:07 PM, Joshua Yanovski <pythonesque@gmail.com> wrote:
>> On Mon, Feb 17, 2014 at 4:33 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> While it would be a reasonably simple change to make this work as
>>> originally intended, I'm strongly tempted to just rip it out instead,
>>> and only support the SQL-mandated syntax.  If anyone was using this
>>> undocumented feature, you'd think they'd have complained sometime in
>>> the last ten years.  And making it work would really entail adding
>>> documentation and a regression test case, so it'd be substantially
>>> more effort than just killing the "list_length == 1" case.
>>>
>>>                         regards, tom lane
>>
>> For what it's worth, that seems reasonable to me as well.  I would
>> never have found this if I weren't actually looking through gram.y
>> anyway.
>>
>> --
>> Josh
>
> Attaching a patch to just remove the n == 1 case.
>
> --
> Josh



--
Josh

Attachment

pgsql-bugs by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: Re: No optimization with a partition window in a view
Next
From: miaoyimin@huawei.com
Date:
Subject: BUG #9265: why the same interval can't get the same timestamp?