Re: Parallel Seq Scan
От | Bert |
---|---|
Тема | Re: Parallel Seq Scan |
Дата | |
Msg-id | CAFCtE1npVAJc5f9xCay6NyfSjygX8Wc1hoyD7N4kXjYv5YDRww@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Parallel Seq Scan (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: Parallel Seq Scan
|
Список | pgsql-hackers |
Hey Robert,
Thank you for the help. As you might (not) know, I'm quite new to the community, but I'm learning. with the help from people like you. This run is compiled from commit 5f10b7a604c87fc61a2c20a56552301f74c9bd5f and your latest patch atteched in this mailtrack.
On Tue, Nov 17, 2015 at 6:55 PM, Robert Haas <robertmhaas@gmail.com> wrote:
On Tue, Nov 17, 2015 at 6:52 AM, Bert <biertie@gmail.com> wrote:
> edit: maybe this is more useful? :)
Definitely. But if you've built with --enable-debug and not stripped
the resulting executable, we ought to get line numbers as well, plus
the arguments to each function on the stack. That would help a lot
more. The only things that get dereferenced in that function are
"scan" and "parallel_scan", so it's a good bet that one of those
pointers is pointing off into never-never land. I can't immediately
guess how that's happening, though.
--
Bert Desmet
0477/305361
0477/305361
В списке pgsql-hackers по дате отправления: