On Tue, Mar 6, 2012 at 7:05 PM, Aleksey Tsalolikhin <atsaloli.tech@xxxxxxxxx> wrote: > We're replicating a PostgreSQL 8.4.x database using Slony1-1.2.x > > The origin database "data/base" directory is 197 GB in size. > > The slave database "data/base" directory is 562 GB in size and is > over 75% filesystem utilization which has set off the "disk free" siren. > > My biggest table* measures 154 GB on the origin, and 533 GB on > the slave. (*As reported by > > SELECT relname as "Table", pg_size_pretty(pg_total_relation_size(relid)) > As "Size" from pg_catalog.pg_statio_user_tables > ORDER BY pg_total_relation_size(relid) DESC; > ) I ran VACUUM FULL on this table, but it is still over 500 GB in size. And growing... I'm up to 77% utilization on the filesystem. "check_postgres --action=bloat" now returns OK. So it's not bloat. What else could it be? Best, Aleksey -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
