Re: BUG #4324: Default value for a column is not returned in select when column has not been explicitly set - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #4324: Default value for a column is not returned in select when column has not been explicitly set
Date
Msg-id 24201.1217093443@sss.pgh.pa.us
Whole thread Raw
In response to BUG #4324: Default value for a column is not returned in select when column has not been explicitly set  ("Jeff Galyan" <jeff@richrelevance.com>)
List pgsql-bugs
"Jeff Galyan" <jeff@richrelevance.com> writes:
> Take an existing table with some data in it and add a nullable column of
> type boolean with default value true.  In 8.2, 'select bool_column from
> my_table' would have returned 'true' for all rows where the column had not
> been explicitly set (which should be all of them at this point).

Works for me:

regression=# create table foo (f1 int);
CREATE TABLE
regression=# insert into foo values(1),(2);
INSERT 0 2
regression=# alter table foo add column b bool default true;
ALTER TABLE
regression=# select * from foo;
 f1 | b
----+---
  1 | t
  2 | t
(2 rows)

Please provide a concrete test case to demonstrate what you are seeing.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Error while loading shared libraries
Next
From: "Sam Wong"
Date:
Subject: BUG #4327: Primary key not refresh after cascaded deleted