| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Daniel Farkaš <daniel(dot)farkas(at)datoris(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17502: View based on window functions returns wrong results when queried |
| Date: | 2022-05-30 02:51:16 |
| Message-ID: | CAApHDvpacAbOTYeTPCgKnafUOvJT0=dFP0q+eVhOhB2Yaa8+QQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, 30 May 2022 at 14:45, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> > On Mon, 30 May 2022 at 14:19, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> I was sort of wondering why we allow SRFs in this context in the
> >> first place. The results don't seem terribly well-defined to me.
>
> > Do you think it would fly to add such a restriction in the backbranches?
>
> We could leave it alone in the back branches on the grounds that if
> you like the results you get, we shouldn't break it in a minor
> release.
I struggle to see how anyone would like their result correctness to
depend on whether remove_unused_subquery_outputs() is able or unable
to remove a column from the subquery.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-05-30 03:02:49 | Re: BUG #17502: View based on window functions returns wrong results when queried |
| Previous Message | Tom Lane | 2022-05-30 02:45:00 | Re: BUG #17502: View based on window functions returns wrong results when queried |