Aleksey,

To answer your questions:

1. So does the database get bigger as it is transfered by Slony?

It doesn't get bigger, but PostgreSQL will write WAL files for all the inserts.
I believe it is the WAL files (16MB each) that is starting to eat up you disk space.

2. how large should the slave's disk be compared to the master's disk?

At least as big as the master. If you intend to use the slave as a failover, it is essential
that the hardware and O/S be as identical as possible.

3. However my database size on the slave is 100 GB, and on the master is 58 GB.

How are you determining this? Are you using df -h?
Or are you doing:

SELECT datname,
       rolname as owner,
       pg_size_pretty(pg_database_size(datname))as size_pretty,
       pg_database_size(datname) as size,
       (SELECT pg_size_pretty (SUM( pg_database_size(datname))::bigint)
          FROM pg_database)  AS total,
       ((pg_database_size(datname) / (SELECT SUM( pg_database_size(datname))
                                       FROM pg_database) ) * 100)::numeric(6,3) AS pct
  FROM pg_database d
  JOIN pg_authid a ON a.oid = datdba
ORDER BY datname;

Also, make sure autovacuum is enabled on the slave?

Melvin Davidson 
  
www.folkalley.com





 
____________________________________________________________________________________
It's here! Your new message!  
Get new email alerts with the free Yahoo! Toolbar.
http://tools.search.yahoo.com/toolbar/features/mail/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20110214/027b10ef/attachment.htm