<html><body><span style="font-family:Verdana; color:#000000; font-size:10pt;"><div><font face="verdana, geneva" size="2" style=""><span style="">Does anyone know, what the names/location of the pg_upgrade cleanup scripts? We upgraded from 8.4.3 to 9.1.6</span></font></div><div><font face="verdana, geneva" size="2" style=""><span style=""><br></span></font></div><div><font face="verdana, geneva" size="2" style=""><span style="">thanks</span></font></div><div><font face="verdana, geneva" size="2" style=""><span style=""><br></span></font></div><blockquote id="replyBlockquote" webmail="1" style="color: black; font-family: verdana; font-size: 10pt; border-left-width: 2px; border-left-style: solid; border-left-color: blue; margin-left: 8px; padding-left: 8px; "><div id="wmQuoteWrapper"><span style="font-family:Verdana; color:#000000; font-size:10pt;"> <div> </div> <blockquote style="BORDER-LEFT: blue 2px solid; PADDING-LEFT: 8px; FONT-FAMILY: verdana; COLOR: black; MARGIN-LEFT: 8px; FONT-SIZE: 10pt" id="replyBlockquote" webmail="1"> <div id="wmQuoteWrapper"><span style="FONT-FAMILY: Verdana; COLOR: #000000; FONT-SIZE: 10pt"> <blockquote style="BORDER-LEFT: blue 2px solid; PADDING-LEFT: 8px; FONT-FAMILY: verdana; COLOR: black; MARGIN-LEFT: 8px; FONT-SIZE: 10pt" id="replyBlockquote" webmail="1"> <div id="wmQuoteWrapper">-------- Original Message --------<br>Subject: Re: [BUGS] Excessive space allocations in Postgresql 9.1.6<br>system files causing the file system to run out of space.<br>From: Kevin Grittner <<a href="mailto:kgrittn(at)ymail(dot)com" target="_blank">kgrittn(at)ymail(dot)com</a>><br>Date: Fri, March 01, 2013 9:00 am<br>To: "<a href="mailto:fburgess(at)radiantblue(dot)com" target="_blank">fburgess(at)radiantblue(dot)com</a>" <<a href="mailto:fburgess(at)radiantblue(dot)com" target="_blank">fburgess(at)radiantblue(dot)com</a>>, Andres<br>Freund <<a href="mailto:andres(at)2ndquadrant(dot)com" target="_blank">andres(at)2ndquadrant(dot)com</a>><br>Cc: "<a href="mailto:pgsql-bugs(at)postgresql(dot)org" target="_blank">pgsql-bugs(at)postgresql(dot)org</a>" <<a href="mailto:pgsql-bugs(at)postgresql(dot)org" target="_blank">pgsql-bugs(at)postgresql(dot)org</a>><br><br>"<a href="mailto:fburgess(at)radiantblue(dot)com" target="_blank">fburgess(at)radiantblue(dot)com</a>" <<a href="mailto:fburgess(at)radiantblue(dot)com" target="_blank">fburgess(at)radiantblue(dot)com</a>> wrote:<br><br>> We did use pg_upgrade with the hard link option. We are not sure<br>> if we ran the cleanup script.<br><br>> Can we run this script now, even though its month's after we did<br>> the upgrade?<br><br>> Everything in the .../19177 directories represent data files<br>> migrated over form postgres 8.4.3. All new files get placed into<br>> the .../PG_9.1_201105231/16411 directories.<br><br>> The vast majority of the "orphan" files are from the<br>> /opt/PostgreSQL/9.1/data/user_data/19177 directory.<br><br>I don't have any reason to expect that you *can't* run the script<br>at this point; but being a cautious person, I would do this at a<br>point where I was confident I could recover from a backup, and I<br>would read through the scripts carefully before applying them.<br><br>What you want to be really careful that you *don't* do is to modify<br>or truncate any of the hard-linked files, as they are quite likely<br>to still be just another name for the same file that is in use for<br>production under the newer version. You want to simply remove the<br>older directory entry pointing to the file.<br><br><a href="http://www.linfo.org/hard_link.html" target="_blank">http://www.linfo.org/hard_link.html</a><br><br>-- <br>Kevin Grittner<br>EnterpriseDB: <a href="http://www.enterprisedb.com/" target="_blank">http://www.enterprisedb.com</a><br>The Enterprise PostgreSQL Company<br><br><br>-- <br>Sent via pgsql-bugs mailing list (<a href="mailto:pgsql-bugs(at)postgresql(dot)org" target="_blank">pgsql-bugs(at)postgresql(dot)org</a>)<br>To make changes to your subscription:<br><a href="http://www.postgresql.org/mailpref/pgsql-bugs" target="_blank">http://www.postgresql.org/mailpref/pgsql-bugs</a><br></div></blockquote></span></div></blockquote></span>
</div>
</blockquote></span></body></html>