Re: Parallel Scan Bug: invalid attnum: 0

From: Steve Randall <srandall(at)s3(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Parallel Scan Bug: invalid attnum: 0
Date: 2016-11-10 13:56:41
Message-ID: CABVd52XMq4FPRtkiAdJ7d0D-Uh+fTVSL3EXtkYZkn6aPNy7xtA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I have been able to reproduce the error in my development environment.
EXPLAIN output is attached. EXPLAIN ANALYZE fails with the error
mentioned.

I have to do a little configuring to get the stack trace logs, but it will
be a couple of weeks before they are ready. Tomorrow I head to San
Francisco for a few days off prior to pgConf.

On Wed, Nov 9, 2016 at 12:50 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Steve Randall <srandall(at)s3(dot)com> writes:
> > running pg 9.6.1 on AWS
> > max_parallel_workers_per_gather = 4
> > This only occurs in some schemas, not all. The affected schemas have
> > approx 1 million rows in the table. Much larger schemas (65 million
> rows)
> > and smaller schemas(100K rows) do not have the problem.
>
> FWIW, I failed to duplicate this from the information provided.
> Can you get us EXPLAIN output for the troublesome case, or does it
> fail before printing the EXPLAIN output? How about a stack trace
> from the errfinish call?
>
> regards, tom lane
>

Attachment Content-Type Size
attnum_explain.txt text/plain 796 bytes

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2016-11-10 15:49:35 Re: Parallel Scan Bug: invalid attnum: 0
Previous Message Tim 2016-11-10 12:53:15 Re: error when installing 9.3.0 on Slackware using slackbuilds