Re: Parallel Seq Scan - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Parallel Seq Scan
Date
Msg-id CA+TgmobxbDuCYkDzcLKx5vqLLjpa-f_Gd+zyhZx4r-+C-uJnHg@mail.gmail.com
Whole thread Raw
In response to Re: Parallel Seq Scan  (Bert <biertie@gmail.com>)
Responses Re: Parallel Seq Scan  (Bert <biertie@gmail.com>)
List pgsql-hackers
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.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Parallel Seq Scan
Next
From: Robert Haas
Date:
Subject: Re: Minor comment improvement to create_foreignscan_plan