Thu Jul 26 04:54:34 PDT 2012
- Previous message: [Slony1-hackers] provider selection in 2.2
- Next message: [Slony1-hackers] sl_log_1 doesn't stop to grow
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Yesterday on our production server, the / partition was fully populated. - Slony 1.2.22 is running on / - our databases files are locate at /var/database - PostgreSQL binaries are located into /opt/PostgresPlus/8.3R2AS/ inside of / partition df -h / /var/database/ Filesystem Size Used Avail Use% Mounted on /dev/mapper/VG1-root 18G 2.1G 16G 12% / /dev/sdf1 253G 176G 78G 70% /var/database Quick workaround was to clean up /tmp (inside of /) However a couple hours ago, while I was trying to build a new set replication hangs. I discovered that sl_log_1 table doesn't stop to growing. (more than 30GB size). I would like to know if there is any temporary files generated by Slony which may explains why this table doesn't stop to grow. I don't know if the two issues are linked. Thanks for any help. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-hackers/attachments/20120726/e0ffe15c/attachment.htm
- Previous message: [Slony1-hackers] provider selection in 2.2
- Next message: [Slony1-hackers] sl_log_1 doesn't stop to grow
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-hackers mailing list