Re: Modifying NOT NULL Constraint - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Modifying NOT NULL Constraint
Date
Msg-id 11373.960957195@sss.pgh.pa.us
Whole thread Raw
In response to Modifying NOT NULL Constraint  ("Dan Wilson" <phpPgAdmin@acucore.com>)
List pgsql-hackers
"Dan Wilson" <phpPgAdmin@acucore.com> writes:
> this was posed as a solutions to modifying the NOT NULL constraint:
>> update pg_attributes set attnotnull = 'f' where oid = oidofnotnullcolumn;
>> vacuum analyze;

attnotnull is where the gold is hidden, all right.  The 'vacuum analyze'
step is mere mumbo-jumbo --- there's no need for that.

> Are there any side effects of which I should be aware before attempting to
> use this?

Changing in that direction should be safe enough.  Turning attnotnull
*on* is a little more dubious, since it won't magically make any
existing null entries in the column go away.  attnotnull just governs
the check that prevents you from storing new nulls.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Adding time to DATE type
Next
From: Bruce Momjian
Date:
Subject: Re: Adding time to DATE type