<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I was hoping someone could help shed some light on whether dead tuples reduce slave<br>performance in terms of keeping up to date with the master.<br><br>I read Shoaib's article<br><br><a href="http://people.planetpostgresql.org/shoaibmir/index.php?/archives/9-Schema-specific-dead-tuples-report.html#extended">http://people.planetpostgresql.org/shoaibmir/index.php?/archives/9-Schema-specific-dead-tuples-report.html#extended</a><br><br>and decided to take a look at our Slony schema. We get once in a while lags of 30 seconds or more and wondered<br>if it had to do with table bloat. We are running Slony 1.2.10 on PostgreSQL 8.2.4.<br><br>The results on the master seemed reasonable every time I looked, i.e., routinely vacuumed.<br><br>However, on one of the slaves I saw a lot of table bloat. Can this hurt performance?<br><br>tii=# select * from deadtup_report;<br>-[ RECORD 2 ]------+--------------------<br>table_name | _tii.sl_confirm<br>table_len | 11214848<br>tuple_count | 7762<br>tuple_len | 403624<br>tuple_percent | 3.6<br>dead_tuple_count | 186290<br>dead_tuple_len | 9687080<br>dead_tuple_percent | 86.38<br>free_space | 315080<br>free_percent | 2.81<br>-[ RECORD 3 ]------+--------------------<br>table_name | _tii.sl_event<br>table_len | 10371072<br>tuple_count | 2915<br>tuple_len | 243012<br>tuple_percent | 2.34<br>dead_tuple_count | 70657<br>dead_tuple_len | 5936368<br>dead_tuple_percent | 57.24<br>free_space | 3640376<br>free_percent | 35.1<br>-[ RECORD 6 ]------+--------------------<br>table_name | _tii.sl_log_2<br>table_len | 148004864<br>tuple_count | 38796<br>tuple_len | 5069174<br>tuple_percent | 3.43<br>dead_tuple_count | 1017334<br>dead_tuple_len | 134977401<br>dead_tuple_percent | 91.2<br>free_space | 1742612<br>free_percent | 1.18<br></body></html>