Re: Excessive space allocations in Postgresql 9.1.6 system files causing the file system to run out of space.

From: <fburgess(at)radiantblue(dot)com>
To: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Excessive space allocations in Postgresql 9.1.6 system files causing the file system to run out of space.
Date: 2013-03-04 19:10:14
Message-ID: 20130304121014.5a830134ae84016b0174832fdc1a3173.90252fcc5c.wbe@email11.secureserver.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

<html><body><span style="font-family:Verdana; color:#000000; font-size:10pt;"><div>Does anyone know, what the names/location of the pg_upgrade cleanup scripts? We upgraded from 8.4.3 to 9.1.6 on linux</div>
<div>&nbsp;</div>
<div>thanks</div>
<div>&nbsp;</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 &lt;<A href="mailto:kgrittn(at)ymail(dot)com" target=_blank>kgrittn(at)ymail(dot)com</A>&gt;<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>" &lt;<A href="mailto:fburgess(at)radiantblue(dot)com" target=_blank>fburgess(at)radiantblue(dot)com</A>&gt;, Andres<BR>Freund &lt;<A href="mailto:andres(at)2ndquadrant(dot)com" target=_blank>andres(at)2ndquadrant(dot)com</A>&gt;<BR>Cc: "<A href="mailto:pgsql-bugs(at)postgresql(dot)org" target=_blank>pgsql-bugs(at)postgresql(dot)org</A>" &lt;<A href="mailto:pgsql-bugs(at)postgresql(dot)org" target=_blank>pgsql-bugs(at)postgresql(dot)org</A>&gt;<BR><BR>"<A href="mailto:fburgess(at)radiantblue(dot)com" target=_blank>fburgess(at)radiantblue(dot)com</A>" &lt;<A href="mailto:fburgess(at)radiantblue(dot)com" target=_blank>fburgess(at)radiantblue(dot)com</A>&gt; wrote:<BR><BR>&gt; We did use pg_upgrade with the hard link option. We are not sure<BR>&gt; if we ran the cleanup script.<BR><BR>&gt; Can we run this script now, even though its month's after we did<BR>&gt; the upgrade?<BR><BR>&gt; Everything in the .../19177 directories represent data files<BR>&gt; migrated over form postgres 8.4.3.&nbsp; All new files get placed into<BR>&gt; the .../PG_9.1_201105231/16411 directories.<BR><BR>&gt; The vast majority of the "orphan" files are from the<BR>&gt; /opt/PostgreSQL/9.1/data/user_data/19177&nbsp; 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.&nbsp; 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></body></html>

Attachment Content-Type Size
unknown_filename text/html 3.4 KB

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2013-03-04 20:37:14 Re: BUG #7914: pg_dump aborts occasionally
Previous Message gloria.evelis 2013-03-04 17:47:09 BUG #7915: problema con postgis 2.0