Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #15247: At 'ALTER TABLE ADD COLUMN fast default' , Set attmissingval to NULL in the pg_attribute, query fail - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #15247: At 'ALTER TABLE ADD COLUMN fast default' , Set attmissingval to NULL in the pg_attribute, query fail
Date
Msg-id 10837.1529418216@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #15247: At 'ALTER TABLE ADD COLUMN fast default' , Set attmissingval to NULL in the pg_attribute, query fail  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
List pgsql-bugs
Tree view 
Andrew Gierth <andrew@tao11.riddles.org.uk> writes:
> "PG" == PG Bug reporting form <noreply@postgresql.org> writes:
>  PG> (4)  update pg_attribute set attmissingval = NULL where attname = 'b';

> Nobody ever claimed that you could update pg_attribute without crashing
> the server; I can think of half a dozen ways to do it.

Specifically, you broke it by not keeping atthasmissing consistent with
attmissingval.  Manually corrupting catalogs like that is not a supported
operation.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Steven Winfield
Date:
Subject: RE: BUG #15248: pg_upgrade fails when a function with an emptysearch_path is encountered
Next
From: Robert Haas
Date:
Subject: Re: row_to_json(), NULL values, and AS