From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Table Rewrite During ALTER TABLE ... ADD COLUMN ... DEFAULT NULL |
Date: | 2014-04-03 04:19:36 |
Message-ID: | 3704.1396498776@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-general |
Amit Langote <amitlangote09(at)gmail(dot)com> writes:
> On Thu, Apr 3, 2014 at 12:54 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Some experimentation suggests that we are smart about "DEFAULT NULL"
>> unless the column type requires a length-coercion cast, in which
>> case the default expression involves a function call, and that doesn't
>> get elided.
> Is there a warning about such behavior in the manual?
> Is it useful to include it somewhere (not sure where though)?
We could just rephrase the ALTER TABLE docs to say that the table
rewrite is avoided if you omit the DEFAULT clause, rather than
saying that a null default works.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2014-04-03 04:26:45 | Re: Table Rewrite During ALTER TABLE ... ADD COLUMN ... DEFAULT NULL |
Previous Message | Amit Langote | 2014-04-03 04:12:18 | Re: Table Rewrite During ALTER TABLE ... ADD COLUMN ... DEFAULT NULL |
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2014-04-03 04:26:45 | Re: Table Rewrite During ALTER TABLE ... ADD COLUMN ... DEFAULT NULL |
Previous Message | Amit Langote | 2014-04-03 04:12:18 | Re: Table Rewrite During ALTER TABLE ... ADD COLUMN ... DEFAULT NULL |