Re: BUG #5145: Complex query with lots of LEFT JOIN causes segfault

Поиск
Список
Период
Сортировка
Искать
От
Greg Stark
Тема
Re: BUG #5145: Complex query with lots of LEFT JOIN causes segfault
Дата
Msg-id
407d949e0910291700s123fa568l1ae2d7506ea38f0e@mail.gmail.com
Ответ на
Список
Дерево обсуждения
BUG #5145: Complex query with lots of LEFT JOIN causes segfault "Bernt Marius Johnsen" <bernt.johnsen@sun.com>
Re: BUG #5145: Complex query with lots of LEFT JOIN causes segfault Euler Taveira de Oliveira <euler@timbira.com>
Re: BUG #5145: Complex query with lots of LEFT JOIN causes segfault "Bernt M. Johnsen" <Bernt.Johnsen@Sun.COM>
Re: BUG #5145: Complex query with lots of LEFT JOIN causes segfault Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
Re: BUG #5145: Complex query with lots of LEFT JOIN causes segfault Tom Lane <tgl@sss.pgh.pa.us>
Re: BUG #5145: Complex query with lots of LEFT JOIN causes segfault Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
Re: BUG #5145: Complex query with lots of LEFT JOIN causes segfault Tom Lane <tgl@sss.pgh.pa.us>
Re: BUG #5145: Complex query with lots of LEFT JOIN causes segfault Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
Re: BUG #5145: Complex query with lots of LEFT JOIN causes segfault Tom Lane <tgl@sss.pgh.pa.us>
Re: BUG #5145: Complex query with lots of LEFT JOIN causes segfault Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
Re: BUG #5145: Complex query with lots of LEFT JOIN causes segfault Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
Re: BUG #5145: Complex query with lots of LEFT JOIN causes segfault Greg Stark <gsstark@mit.edu>
Re: BUG #5145: Complex query with lots of LEFT JOIN causes segfault Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
Re: BUG #5145: Complex query with lots of LEFT JOIN causes segfault Tom Lane <tgl@sss.pgh.pa.us>
Re: BUG #5145: Complex query with lots of LEFT JOIN causes segfault Tom Lane <tgl@sss.pgh.pa.us>
Re: BUG #5145: Complex query with lots of LEFT JOIN causes segfault Greg Stark <gsstark@mit.edu>
On Thu, Oct 29, 2009 at 2:14 PM, Stefan Kaltenbrunner
 wrote:
> ExecHashJoinSaveTuple (tuple=3D0xb49c8870, hashvalue=3D3316173823,
> fileptr=3D0x96185a8) at nodeHashjoin.c:775
> 775 =A0 =A0 =A0 =A0 =A0 =A0 BufFile =A0 =A0*file =3D *fileptr;
>

That back trace doesn't make much sense. That function only has one
call site and it's called with fileptr set to an expression starting
with &. Ie, there's no way it can get null or an invalid pointer.

--=20
greg
В списке pgsql-bugs по дате отправления
От: Tom Lane
Дата:
От: Stefan Kaltenbrunner
Дата:
FAQ