Let's say you drop a column on a table. Then you dump
that table and load it into a slave server. Then you
create dbmirror trigger on master database. Then
dbmirror goes by original definition of master table
before the column was dropped. In particular it is
looking for a column "........pg.dropped.2........"
where 2 is the column number that was dropped. What
is really terrible is that not only does it generate
errors and stop mirroring this table it also stops
mirroring all other tables!!
I tried to "VACUUM FULL" the table hoping that
"........pg.dropped.2........" will be gotten rid of
from a low level definition of this table which
dbmirror is referring but no luck. "VACUUM FULL" does
not get rid of that dropped column from some kind of
system data which dbmirror is referring to.
Is the only way out of this problem dumping the master
table and reloading? The table is a live one (being
inserted every second on average) and I prefer to
minimize interruptions
Thanks
__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/