[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pgsql-bugs
Subject:    Re: [BUGS] BUG #4125: Strange ALTER TABLE behavior
From:       Vladimir Kanazir <vladimir () vlajko ! com>
Date:       2008-04-23 15:49:37
Message-ID: 200804231749.37767.vladimir () vlajko ! com
[Download RAW message or body]


> > But, if I do this:
> > alter table history add incoming_id bigint;
> > alter table history alter incoming_id set default 0;
> > update history set incoming_id=0;
> > the table will be locked only during alter table execution, which
> > is very short time.
>
> But this exposes the state where incoming_id isn't zero to other
> transactions.

Yes, I can see your point... But if there is a system running, this will 
lock it up even current transactions doesn't care about the new field. 
That is how I noticed this :)

But, I guess, you can't make everybody happy :)
Thanks
-- 
Regards
Vladimir Kanazir

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
[prev in list] [next in list] [prev in thread] [next in thread]