From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | Hannu Krosing <hannu(at)skype(dot)net> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: effective SELECT from child tables |
Date: | 2005-10-02 05:24:07 |
Message-ID: | 871x34cwzs.fsf@stark.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hannu Krosing <hannu(at)skype(dot)net> writes:
> I also often wish that this would be possible when someone adds a column
> with a default value to a multi-million row table on a 24/7 production
> system and insists on filling all existing columns with the default.
>
> A rule "ON SELECT FROM table_x WHERE col_x IS NULL return
> col_x=default_for_col_x" would solve that nicely.
Of course that only works if the reason they want to set fill the rows with
the default value isn't precisely because NULL is a perfectly reasonable thing
for the column to have (but not what they want for the existing rows).
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Hallgren | 2005-10-02 07:46:27 | Re: Socket problem using beta2 on Windows-XP |
Previous Message | Tom Lane | 2005-10-02 03:26:07 | Re: [PERFORM] A Better External Sort? |