Re: BUG #19904: pg_column_is_updatable(): "negative bitmapset member not allowed" for large attnum (int16 overflow)

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: hackerzheng666(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19904: pg_column_is_updatable(): "negative bitmapset member not allowed" for large attnum (int16 overflow)
Date: 2026-11-18 20:10:35
Message-ID: CAApHDvqJNTo6TLdT9Dz7yrxKRcyG72syypQQ7rM-8T5Wo-V=sg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, 17 Nov 2026 at 16:55, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
>
> On Tue, 17 Nov 2026 at 00:45, PG Bug reporting form
> <noreply(at)postgresql(dot)org> wrote:
> > create table tt(a int, b text);
> > select pg_column_is_updatable('tt'::regclass, 32767::smallint, true);
> > ERROR: negative bitmapset member not allowed
>
> We could fix by just promoting the AttrNumber to int with:

Pushed. Thanks.

David

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message David Rowley 2026-11-18 21:29:27 Re: BUG #19915: Qual over function-wrapped grouping column pushed past DISTINCT ON returns wrong rows
Previous Message João Rito 2026-11-18 19:03:35 Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY