Re: An oversight in ExecInitAgg for grouping sets
От | Tom Lane |
---|---|
Тема | Re: An oversight in ExecInitAgg for grouping sets |
Дата | |
Msg-id | 1650235.1672694719@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: An oversight in ExecInitAgg for grouping sets (Richard Guo <guofenglinux@gmail.com>) |
Ответы |
Re: An oversight in ExecInitAgg for grouping sets
Re: An oversight in ExecInitAgg for grouping sets |
Список | pgsql-hackers |
Richard Guo <guofenglinux@gmail.com> writes: > On Thu, Dec 22, 2022 at 2:02 PM Richard Guo <guofenglinux@gmail.com> wrote: >> If it is an empty grouping set, its length will be zero, and accessing >> phasedata->eqfunctions[length - 1] is not right. > Attached is a trivial patch for the fix. Agreed, that's a latent bug. It's only latent because the word just before a palloc chunk will never be zero, either in our historical palloc code or in v16's shiny new implementation. Nonetheless it is a horrible idea for ExecInitAgg to depend on that fact, so I pushed your fix. The thing that I find really distressing here is that it's been like this for years and none of our automated testing caught it. You'd have expected valgrind testing to do so ... but it does not, because we've never marked that word NOACCESS. Maybe we should rethink that? It'd require making mcxt.c do some valgrind flag manipulations so it could access the hdrmask when appropriate. regards, tom lane
В списке pgsql-hackers по дате отправления: