Re: Oversight in reparameterize_path_by_child leading to executor crash
От | Robert Haas |
---|---|
Тема | Re: Oversight in reparameterize_path_by_child leading to executor crash |
Дата | |
Msg-id | CA+TgmobYKXms735aKynRdJcVziyRCLbDsUvOMFVXF-Ned+rmwg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Oversight in reparameterize_path_by_child leading to executor crash (Richard Guo <guofenglinux@gmail.com>) |
Ответы |
Re: Oversight in reparameterize_path_by_child leading to executor crash
Re: Oversight in reparameterize_path_by_child leading to executor crash |
Список | pgsql-hackers |
On Mon, Jan 8, 2024 at 3:32 AM Richard Guo <guofenglinux@gmail.com> wrote: > Thanks for the suggestion. Attached is an updated patch which is added > with a commit message that tries to explain the problem and the fix. This is great. The references to "the sampling infos" are a little bit confusing to me. I'm not sure if this is referring to TableSampleClause objects or what. > Fair point. I think we can back-patch a more minimal fix, as Tom > proposed in [1], which disallows the reparameterization if the path > contains sampling info that references the outer rel. But I think we > need also to disallow the reparameterization of a path if it contains > restriction clauses that reference the outer rel, as such paths have > been found to cause incorrect results, or planning errors as in [2]. Do you want to produce a patch for that, to go along with this patch for master? I know this is on Tom's to-do list which makes me a bit reluctant to get too involved here, because certainly he knows this code better than I do, maybe better than anyone does, but on the other hand, we shouldn't leave server crashes unfixed for too long, so maybe I can do something to help at least with that part of it. -- Robert Haas EDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: