<div dir="ltr"><div class="gmail_extra">Postgres 9.4.5 slon 2.2.3 CentOS 6.6</div><div class="gmail_extra"><br></div><div class="gmail_extra">Afternoon</div><div class="gmail_extra"><br></div><div class="gmail_extra">Based on some searching this is not new, but I have failed to find an answer for it.. I had an index running on a non replicated table but slon would not initialize due to that index, something about set 1 failed due to a previous PID.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Now I'm trying to to reindex 2 tables that are not in the slon relationship, but slon is backing up, once I stop the reindex, slon replicates just fine (immediately). Something is wonky (its a technical term, you can look it up!: ) )</div><div class="gmail_extra"><br></div><div class="gmail_extra">So killing the index, I was able to add my host, but now I'm trying to add another 2 indexes and it's backing up slon, and or one is holding up the other.</div><div class="gmail_extra"><br></div><div class="gmail_extra">So now I'm trying to create 2 indexes concurrently...</div><div class="gmail_extra">
<p class=""><span class="">These are the 2 i am creating. </span></p>
<p class=""><span class="">One is waiting on the other. (Waiting is true in pg_stat_Activity)</span></p>
<p class=""><span class="">If I kill the 1st the second starts. Nothing is querying this table.</span></p>
<p class=""><br><span class=""></span></p><p class=""><span class=""></span></p>
<p class=""><span class="">CREATE INDEX CONCURRENTLY idx_impsarchive_psttstamp</span></p>
<p class=""><span class=""> ON torque.impressions_archive</span></p>
<p class=""><span class=""> USING btree</span></p>
<p class=""><span class=""> (timezone('US/Pacific'::text, timezone('UTC'::text, log_tstamp)))</span></p>
<p class=""><span class="">TABLESPACE torquespace;</span></p>
<p class=""><span class=""></span><br></p>
<p class=""><span class="">-- Index: torque.idx_impsarchive_system</span></p>
<p class=""><span class=""></span><br></p>
<p class=""><span class="">-- DROP INDEX torque.idx_impsarchive_system;</span></p>
<p class=""><br></p><p class="">CREATE INDEX CONCURRENTLY idx_impsarchive_system<br><span class=""></span></p>
<p class=""><span class=""> ON torque.impressions_archive</span></p>
<p class=""><span class=""> USING btree</span></p>
<p class=""><span class=""> (system COLLATE pg_catalog."default")</span></p>
<p class=""><span class="">TABLESPACE torquespace;</span></p>
<p class=""><span class=""></span><br></p>
<p class=""><span class="">Also when I had it running non-concurrently they both ran at the same time. But slony got backed up. It didn’t explicitly say that it was waiting. But after about 45 minutes, data had not replicated. I killed the indices and it replicated immediately. This table is not being replicated. </span></p>
<p class=""><span class=""><i></i></span><br></p>
<p class=""><span class="">I also queried sl_table on the master and this table is not there</span></p>
<p class=""><span class=""></span><br></p>
<p class=""><span class=""><i> tab_id | tab_reloid | tab_relname | tab_nspname | tab_set | tab_idxname | tab_altered | tab</i></span></p>
<p class=""><span class=""><i>_comment </i></span></p>
<p class=""><span class=""><i>--------+------------+---------------------+-------------+---------+--------------------------+-------------+-----------</i></span></p>
<p class=""><span class=""><i>-----------------</i></span></p>
<p class=""><span class=""><i> 225 | 17959 | variables | torque | 2 | pk_variables_name | f | replicated</i></span><i>table</i></p>
<p class=""><span class=""><i> 226 | 17935 | impsbulkimporteven | torque | 2 | pk_impsbulkimporteven_id | f | torque.imp</i></span><i>sbulkimporteven</i></p>
<p class=""><span class=""><i> 228 | 17947 | impsbulkimportodd | torque | 2 | pk_impsbulkimportodd_id | f | torque.imp</i></span><i>sbulkimportodd</i></p>
<p class=""><span class=""><i> 233 | 17919 | impressions_daily | torque | 2 | pk_impsdaily_id | f | torque.i</i></span><i>mpressions_daily</i></p>
<p class=""><span class=""><i> 235 | 17907 | impressions | torque | 2 | pk_impressions_id | f | torque.i</i></span><i>mpressions</i></p>
<p class=""><span class=""><i>(5 rows)</i></span></p></div><div class="gmail_extra"><br></div><div class="gmail_extra">So I want to create these indexes, they are not being replicated but they completely freeze replication. Same thing happened when I added a node, slon would not initialize until we killed the same index creation on this same non replicated table. I'm not sure what is going on and my apologies i deleted the set 1 failed, due to a previous pid message, but if this table is not in replication, why is it causing slon to be blocked?</div><div class="gmail_extra"><br></div><div class="gmail_extra">Thanks</div><div class="gmail_extra">Tory</div><div class="gmail_extra"><br></div></div>