Thread: Re: Excessive space allocations in Postgresql 9.1.6 system files causing the file system to run out of space.
<span style=3D"font-family:Verdana; color:#000000; font-size:10= pt;"><span style= =3D"">Does anyone know, what the names/location of the pg_upgrade cleanup s= cripts? We upgraded from 8.4.3 to 9.1.6<font face= =3D"verdana, geneva" size=3D"2" style=3D""></fo= nt><span st= yle=3D"">thanks<font face=3D"verdana, geneva" size= =3D"2" style=3D""><blockquote id= =3D"replyBlockquote" webmail=3D"1" style=3D"color: black; font-family: verd= ana; font-size: 10pt; border-left-width: 2px; border-left-style: solid; bor= der-left-color: blue; margin-left: 8px; padding-left: 8px; "><div id=3D"wmQ= uoteWrapper"><span style=3D"font-family:Verdana; color:#000000; font-size:1= 0pt;"> <blockquote style=3D"BORDER-LEFT: blue 2px solid; = PADDING-LEFT: 8px; FONT-FAMILY: verdana; COLOR: black; MARGIN-LEFT: 8px; FO= NT-SIZE: 10pt" id=3D"replyBlockquote" webmail=3D"1"> <div id=3D"wmQuoteWrap= per">= <blockquote style=3D"BORDER-LEFT: blue 2px solid; PADDING-LEFT: 8px; FONT-= FAMILY: verdana; COLOR: black; MARGIN-LEFT: 8px; FONT-SIZE: 10pt" id=3D"rep= lyBlockquote" webmail=3D"1"> -------- Original M= essage --------Subject: Re: [BUGS] Excessive space allocations in Postg= resql 9.1.6system files causing the file system to run out of space.<br= >From: Kevin Grittner <<a href=3D"mailto:kgrittn@ymail.com" target=3D"_b= lank">kgrittn@ymail.com>Date: Fri, March 01, 2013 9:00 amTo:= "fburgess@ra= diantblue.com" <<a href=3D"mailto:fburgess@radiantblue.com" target= =3D"_blank">fburgess@radiantblue.com>, AndresFreund <<a href= =3D"mailto:andres@2ndquadrant.com" target=3D"_blank">andres@2ndquadrant.com= >Cc: "<a href=3D"mailto:pgsql-bugs@postgresql.org" target=3D"_bl= ank">pgsql-bugs@postgresql.org" <<a href=3D"mailto:pgsql-bugs@postgr= esql.org" target=3D"_blank">pgsql-bugs@postgresql.org>"<a hr= ef=3D"mailto:fburgess@radiantblue.com" target=3D"_blank">fburgess@radiantbl= ue.com" <<a href=3D"mailto:fburgess@radiantblue.com" target=3D"_blan= k">fburgess@radiantblue.com> wrote:> We did use pg_upgrad= e with the hard link option. We are not sure> if we ran the cleanup = script.> Can we run this script now, even though its month's aft= er we did> the upgrade?> Everything in the .../19177 dire= ctories represent data files> migrated over form postgres 8.4.3.&nbs= p; All new files get placed into> the .../PG_9.1_201105231/16411 dir= ectories.> The vast majority of the "orphan" files are from the<= br>> /opt/PostgreSQL/9.1/data/user_data/19177 directory.I = don't have any reason to expect that you *can't* run the scriptat this = point; but being a cautious person, I would do this at apoint where I w= as confident I could recover from a backup, and Iwould read through the= scripts carefully before applying them.What you want to be really = careful that you *don't* do is to modifyor truncate any of the hard-lin= ked files, as they are quite likelyto still be just another name for th= e same file that is in use forproduction under the newer version. = You want to simply remove theolder directory entry pointing to the fil= e.<a href=3D"http://www.linfo.org/hard_link.html" target=3D"_blank"= >http://www.linfo.org/hard_link.html-- Kevin GrittnerEn= terpriseDB: http= ://www.enterprisedb.comThe Enterprise PostgreSQL Company<br= >-- Sent via pgsql-bugs mailing list (<a href=3D"mailto:pgsql-bugs@post= gresql.org" target=3D"_blank">pgsql-bugs@postgresql.org)To make cha= nges to your subscription:<a href=3D"http://www.postgresql.org/mailpref= /pgsql-bugs" target=3D"_blank">http://www.postgresql.org/mailpref/pgsql-bug= s =0A=0A<= /blockquote>
Re: Excessive space allocations in Postgresql 9.1.6 system files causing the file system to run out of space.
From
Kevin Grittner
Date:
"fburgess@radiantblue.com" <fburgess@radiantblue.com> wrote:=0A=0A> Does an= yone know, what the names/location of the pg_upgrade=0A> cleanup scripts? W= e upgraded from 8.4.3 to 9.1.6=0A=0ASorry I didn't answer this sooner, but = I didn't know off-hand and=0Ahoped that someone who did would jump in.=A0 S= ince that didn't happen=0A...=0A=0AThe file is delete_old_cluster.sh on mos= t platforms.=A0 The suffix is=0A.bat on Windows.=0A=0AIt can be run anytime= after the upgrade *as long as you have not=0Amoved the new cluster to the = old location*.=0A=0AThanks to Bruce Momjian for telling me in chat when I a= sked just now.=0A=0A--=0AKevin Grittner=0AEnterpriseDB: http://www.enterpri= sedb.com=0AThe Enterprise PostgreSQL Company