On Thu, Jun 08, 2006 at 11:42:49AM -0400, Greg Stark wrote: > > > It was awfully annoying for users when that feature was missing. > > > Any non-linearities in the user interface like this > > > end up being surprises and annoyances for users. > > > > I would be *really*, *really*, *really* annoyed if an op that I expected > > to take less than 1 sec takes 5 hours and then forces me to spend > > another 10 hours on VACUUM FULL+REINDEX or CLUSTER to get performance > > back. > > I forget whether the developer managed to get it working without doing any > table rewriting. In theory the table just needs to know that records that are > "missing" that column in the null bitmap should behave as if they have the > default value. But I seem to recall some headaches with that approach.
What happens if you ALTER TABLE ... ADD new_column int DEFAULT 1; ALTER TABLE ... ALTER new_column SET DEFAULT 2; -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
