Re: BUG #5614: Varchar column (with DEFAULT NULL) stores 'UL' value instead of null

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Mariusz Majer" <mmajer(at)janmedia(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5614: Varchar column (with DEFAULT NULL) stores 'UL' value instead of null
Date: 2010-08-12 18:26:51
Message-ID: 2675.1281637611@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Mariusz Majer" <mmajer(at)janmedia(dot)com> writes:
> There has been a table ecom2_orders for a while (~0.5m records). After
> executing query:

> ALTER TABLE ecom2_orders ADD COLUMN password_pdf character varying(50);

> when new rows are added, column password_pdf is filled with 'UL' value
> rather than null

Works fine here. Perhaps you have an incorrect build of 8.3.11?

Another possibility is that you omitted some important step.
Ordinarily, \d wouldn't show any explicit "default" modifier for a
column created as above. Maybe you did an ALTER SET DEFAULT in a
strange way?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2010-08-12 20:39:54 Re: BUG #5613: cannot delete
Previous Message Robert Haas 2010-08-12 16:57:15 Re: BUG #5611: SQL Function STABLE promoting to VOLATILE