From: | Joshua Yanovski <pythonesque(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #9227: Error on SELECT ROW OVERLAPS ROW with single ROW argument |
Date: | 2014-02-18 01:07:26 |
Message-ID: | CABz-M-EGDwHUmG7G0rPEL3KzgauoL99F7f7EcWYt1gAst2MMMw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, Feb 17, 2014 at 4:33 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro HORIGUCHI | 2014-02-18 02:50:22 | Re: No optimization with a partition window in a view |
Previous Message | Tom Lane | 2014-02-18 00:33:13 | Re: BUG #9227: Error on SELECT ROW OVERLAPS ROW with single ROW argument |