Re: BUG #16111: Unexpected query compilation error “negative bitmapset member not allowed”

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
Cc: tuomas(dot)leikola(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16111: Unexpected query compilation error “negative bitmapset member not allowed”
Date: 2019-12-05 00:38:23
Message-ID: 20191205003823.GB2082@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, Nov 16, 2019 at 02:36:42AM +0100, Tomas Vondra wrote:
> >Yeah, this is a bug in estimate_multivariate_ndistinct, which fails to
> >ignore system attributes :-(
> >
> >The attached patch fixes it, but unfortunatly we've missed this round of
> >minor releases :-( I'll get it pushed in a couple of days.
> >
> >Thanks for the report and the reproducer, very helpful!
>
> I've pushed the fix, after a minor improvement (it wasn't quite right,
> because the bitmap was updated again a bit later). Backpatched to 10+.

I thought you'd be interested to know I just ran into this myself, so I
would've reported it now, if it hadn't already been fixed - thanks.

-- Note, that's actually a table named after a view..
ts=# explain SELECT tableoid::regclass FROM daily_enodeb_baseband_view GROUP BY 1;
ERROR: negative bitmapset member not allowed

--
Justin Pryzby
System Administrator
Telsasoft
+1-952-707-8581

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Geoghegan 2019-12-05 01:10:20 Re: BUG #16140: View with INSERT, DO INSTEAD, and ON CONFLICT causes an error
Previous Message PG Bug reporting form 2019-12-05 00:21:36 BUG #16149: Prepared COPY queries always report 0 parameters when described