Dear Melvin,<br><br> Thanks for answering my questions. <br><br> My slave has same hardware configuration as the master.<br><br> I ran the SQL command you sent, and it reports database size <br>100 GB on the slave. Same SQL command reports 58 GB on <br>
the master.<br><br> I tried VACUUM FULL on the database, but the size remains<br>100 GB.<br><br> The following command tells me that 97 GB is used by my large<br>table and its TOAST and index:<br><br> SELECT relname as "Table", pg_size_pretty(pg_total_relation_size(relid)) <br>
As "Size" from pg_catalog.pg_statio_user_tables <br> ORDER BY pg_total_relation_size(relid) DESC;<br><br><br>
My disk on the slave is nearly full (only a couple of GB free) so<br>when I get a maintenance window, I will try dropping my large table <br>(which is 45 GB on production) from
replication, and then add it back,<br>maybe it will come back smaller? <br><br> I would like to understand why it's larger on the slave.<br><br>Aleksey<br><br>