Re: BUG #13781: "unrecognized node type" errors

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: zsolt(dot)sandor(at)gmail(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #13781: "unrecognized node type" errors
Date: 2015-11-23 20:02:46
Message-ID: 11440.1448308966@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

zsolt(dot)sandor(at)gmail(dot)com writes:
> The problem didn't occur in 9.4.4, but does consistently on 9.4.5. The "bt
> full" output is as follows:

This stack trace is pretty wacko; in particular, frames 13-17 imply that
you've got a Query whose jointree field is pointing directly at an
AccessPriv node, and then the AccessPriv node's cols field is pointing
directly at a BoolExpr. None of that makes any sense at all. The most
likely explanation is that the debugger is not telling the truth (perhaps
you've pointed it to the wrong executable?), in which case there's exactly
zero trustworthy information here.

A different line of theorization is that the querytree read back from the
system catalogs for the view that's evidently getting expanded is corrupt
somehow. You might look at whether psql's \d+ on the view produces a
sane-looking query.

Please see if you can extract a reproducible test case. It's not very
likely that anybody will be able to help on the strength of the
information you have provided.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message jkew 2015-11-23 21:04:56 BUG #13782: gss auth with libpq does not include realm by default
Previous Message Caleb Meredith 2015-11-23 15:19:49 Re: BUG #13780: Multiple commands not allowed for creating a policy.