<br><br><div class="gmail_quote">On Sun, Feb 13, 2011 at 8:08 PM, Melvin Davidson <span dir="ltr"><<a href="mailto:melvin6925@yahoo.com">melvin6925@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<table border="0" cellpadding="0" cellspacing="0"><tbody><tr><td style="font: inherit;" valign="top"><font size="3">Aleksey,<br><br>I can't really say how much disk space PostgreSQL 8.4 will use when processing the 45GB table. However, I did go back and look at your initial report and disk configuration. <br>
<div class="im"><br><span style="font-family: courier,monaco,monospace,sans-serif;"># df -h</span><br style="font-family: courier,monaco,monospace,sans-serif;"><span style="font-family: courier,monaco,monospace,sans-serif;">Filesystem Size Used Avail Use% Mounted on</span><br style="font-family: courier,monaco,monospace,sans-serif;">
<span style="font-family: courier,monaco,monospace,sans-serif;">/dev/sda3 <span style="font-weight: bold; color: rgb(192, 0, 0);">117G</span> 110G 1.3G 99% /</span><br style="font-family: courier,monaco,monospace,sans-serif;">
<span style="font-family: courier,monaco,monospace,sans-serif;">/dev/sda1 99M 24M 71M 26% /boot</span><br style="font-family: courier,monaco,monospace,sans-serif;"><span style="font-family: courier,monaco,monospace,sans-serif;">tmpfs 3.9G 0 3.9G 0% /dev/shm</span><br style="font-family: courier,monaco,monospace,sans-serif;">
<br></div>You indicated your master has a 58GB database. Right at the start it means you will be using about half the available space. Add to that WAL files, system files, PostgreSQL binaries, etc, and it's easy to see that you will be using a large percentage of the only disk available. <br>
<br>The best I can recommend would be to try increasing checkpoint_segments ( try 20) temporarily. However, you
might also look into just adding a larger disk (250GB?) or at least replacing the 117GB disk with a larger one. </font><br></td></tr></tbody></table></blockquote><div><br>Dear Melvin,<br><br> Point taken. Thanks for your time to look at my issue.<br>
<br> This is how my master's disk free looks:<br><br>Filesystem Size Used Avail Use% Mounted on<br>/dev/sda3 124G 87G 32G 74% /<br><br> So does the database get bigger as it is transfered by Slony? In other words, does the replication have a disk utilization overhead? If so, how large should the slave's disk be compared to the master's disk?<br>
<br> I had already increased checkpoint_segments from the default 3 to 24. I tried doubling it to 48. Now apparently my replication is back up. (Bucardo check_postgres script runs OK, and I am seeing updates come across.)<br>
<br> However my database size on the slave is 100 GB, and on the master is 58 GB. What happened? How do I get it back down? <br><br>/var/lib/pgsql/data/base/25219965 on the Slave contains 48 files, each 1.1 GB in size,<br>
and an 8.0KB PGVERSION file. but "du -sh 25219965" says 101GB. <br><br>I'm definitely going to upgrade the disk subsystem on both servers as soon as possible (I've already requested the funding). Thanks for the hint re checkpoint_segments.<br>
<br>I don't understand how I went so quickly from the COPY failing to replication being up to date.<br><br>I will have to check tomorrow to make sure everything is there (on the slave) that should be there.<br><br>Thanks!! I really appreciate the help.<br>
Aleksey<br><br><br><br></div></div>