Re: BUG #14169: Incorrect merge join result in 9.5
От | Tom Lane |
---|---|
Тема | Re: BUG #14169: Incorrect merge join result in 9.5 |
Дата | |
Msg-id | 4417.1464890956@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: BUG #14169: Incorrect merge join result in 9.5 (Kevin Grittner <kgrittn@gmail.com>) |
Список | pgsql-bugs |
Kevin Grittner <kgrittn@gmail.com> writes: > On Wed, Jun 1, 2016 at 11:15 AM, Kevin Grittner <kgrittn@gmail.com> wrote: >> On Wed, Jun 1, 2016 at 11:10 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >>> In short: Kevin, you broke mark/restore. Please fix. >> I'm on it. > Fix pushed. I confirm this fixes the submitted test case. > Basically, I reverted an attempt to optimize repeated > restores to the same page. I had a rather bad thinko there where I > essentially assumed that it was also to the same mark, so advancing > marks on the same page caused the bug. There's probably room to > optimize that with more refined logic, but for now I just reverted > the problem code. Sounds reasonable. The comments in that removed hunk of code had made me suspicious as heck the moment I saw them ... > I reduced the test case supplied by the OP to something smaller > which still failed the assertion without the patch, but am having > trouble getting it to run in the regression test environment with a > stable plan. Best bet might be to use a temp table, so that autoanalyze won't touch it. regards, tom lane
В списке pgsql-bugs по дате отправления: