Sun Feb 13 17:45:46 PST 2011
- Previous message: [Slony1-general] unable to set up replication: slony1-1.2.21: sync of large table (45 GB) fails: sequence maxed out
- Next message: [Slony1-general] unable to set up replication: slony1-1.2.21: sync of large table (45 GB) fails: sequence maxed out
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sun, Feb 13, 2011 at 2:17 PM, Melvin Davidson <melvin6925 at yahoo.com>wrote: > >OK, same thing happened: disk usage on the Slony slave is now 96%, and > >this is while COPY of our large table (over 45 GB in size) is running. > > 106 GB is used on disk. > > >Any suggestions, please? > > Is WAL archiving enabled on the slave? If so, turn it off, restart > postgresql on the slave, then try replicating. > Thanks, Melvin. WAL archiving is disabled on both servers. (archive_mode = off). How much disk space should I expect Postgres (8.4.4) to use when receiving a 45 GB table via Slony? Best, Aleksey -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20110213/fc885960/attachment.htm
- Previous message: [Slony1-general] unable to set up replication: slony1-1.2.21: sync of large table (45 GB) fails: sequence maxed out
- Next message: [Slony1-general] unable to set up replication: slony1-1.2.21: sync of large table (45 GB) fails: sequence maxed out
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list