<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">What does your table stest look like on the replica? Does it have a column "name" ?<br>
<br>
What DDL did you execute and in what order? If you are adding or dropping the "name" column then this sounds like a bug, but more details so we can reproduce this would be helpful.<div class="im"></div></blockquote>
<div><br></div><div><div>Sure. I have created a test case and implemented on both slony versions, stabled(2.1.2) & BETA(2.2.0).</div><div><br></div><div>Steps:</div><div>1. Create a table with one column and few rows:</div>
<div> create table stest(id int primary key);</div><div> insert into stest values(generate_series(1,5));</div><div>2. Configure slony (initialization, create & subscribe) in SLON ARCHIVE mode(slon -a).</div><div>
3. Once sync catch up, execute DDL command without using EXECUTE SCRIPT (like user error)</div><div>ALTER TABLE STEST ADD COLUMN NAME TEXT;</div><div>INSERT INTO STEST VALUES (10,'TEST);</div><div><br></div><div>Observations in Slony 2.1.2 on above scenario:</div>
<div><br></div><div>1. DDL caused replication to crash if its executed without using EXECUTE SCRIPT(expected behavior) . Below log message is example of crash when I executed a DDL. </div><div><br></div><div>2013-06-15 16:36:26 IST ERROR remoteWorkerThread_1: "insert into "public"."stest" ("id","name") values (10,'TEST');</div>
<div>" ERROR: column "name" of relation "stest" does not exist</div><div>LINE 1: insert into "public"."stest" ("id","name") values ('1','...</div>
<div>....</div><div>2013-06-15 16:36:26 IST ERROR remoteWorkerThread_1: SYNC aborted</div><div><br></div><div>2. Archives didn't captured the ALTER TABLE command, however an INSERT immediate after ALTER has been captured in archives. </div>
<div>-bash-4.1$ fgrep -i alter *</div><div>-bash-4.1$ fgrep -i insert *</div><div>slony1_log_2_00000000000000000021.sql.tmp:insert into "public"."stest" ("id","name") values ('10','TEST');</div>
<div><br></div><div>Observation in 2.2.0B on above scenario:</div><div><br></div><div>1. Executing DDL, didn't impact the replication whatsoever, in the sense it didn't crashed. It just paused the replication. (I waited for almost 15 minuts and tried few DMLs on the table).</div>
<div>2. Interesting, neither DDL nor DML's captured by archives in this version.</div><div>-bash-4.1$ fgrep -i alter *</div><div>-bash-4.1$ fgrep -i insert *</div><div>-bash-4.1$</div><div><br></div><div>Please let me know if any further information required from my end.</div>
</div><div><br></div><div>--Raghav</div></div>