Re: Excessive space allocations in Postgresql 9.1.6 system files causing the file system to run out of space.
От | |
---|---|
Тема | Re: Excessive space allocations in Postgresql 9.1.6 system files causing the file system to run out of space. |
Дата | |
Msg-id | 20130304121014.5a830134ae84016b0174832fdc1a3173.90252fcc5c.wbe@email11.secureserver.net обсуждение исходный текст |
Список | pgsql-bugs |
<span style=3D"font-family:Verdana; color:#000000; font-size:10= pt;">Does anyone know, what the names/location of the pg_upgrade clean= up scripts? We upgraded from 8.4.3 to 9.1.6 on linux=0A </d= iv>=0Athanks=0A =0A<BLOCKQUOTE style=3D"BORDER-L= EFT: blue 2px solid; PADDING-LEFT: 8px; FONT-FAMILY: verdana; COLOR: black;= MARGIN-LEFT: 8px; FONT-SIZE: 10pt" id=3DreplyBlockquote webmail=3D"1">=0A<= DIV id=3DwmQuoteWrapper><SPAN style=3D"FONT-FAMILY: Verdana; COLOR: #000000= ; FONT-SIZE: 10pt">=0A<BLOCKQUOTE style=3D"BORDER-LEFT: blue 2px solid; PAD= DING-LEFT: 8px; FONT-FAMILY: verdana; COLOR: black; MARGIN-LEFT: 8px; FONT-= SIZE: 10pt" id=3DreplyBlockquote webmail=3D"1">=0A= -------- Original Message --------Subject: Re: [BUGS] Excessive space a= llocations in Postgresql 9.1.6system files causing the file system to r= un out of space.From: Kevin Grittner <<A href=3D"mailto:kgrittn@ymai= l.com" target=3D_blank>kgrittn@ymail.com>Date: Fri, March 01, 20= 13 9:00 amTo: "<A href=3D"mailto:fburgess@radiantblue.com" target=3D_bl= ank>fburgess@radiantblue.com" <<A href=3D"mailto:fburgess@radiantblu= e.com" target=3D_blank>fburgess@radiantblue.com>, AndresFreund &= lt;andres@2ndquad= rant.com>Cc: "<A href=3D"mailto:pgsql-bugs@postgresql.org" targe= t=3D_blank>pgsql-bugs@postgresql.org" <<A href=3D"mailto:pgsql-bugs@= postgresql.org" target=3D_blank>pgsql-bugs@postgresql.org>"<= A href=3D"mailto:fburgess@radiantblue.com" target=3D_blank>fburgess@radiant= blue.com" <<A href=3D"mailto:fburgess@radiantblue.com" target=3D_bla= nk>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.h= ttp://www.linfo.org/hard_link.html-- Kevin GrittnerEnte= rpriseDB: http://w= ww.enterprisedb.comThe Enterprise PostgreSQL Company-- = Sent via pgsql-bugs mailing list (<A href=3D"mailto:pgsql-bugs@postgres= ql.org" target=3D_blank>pgsql-bugs@postgresql.org)To make changes t= o your subscription:<A href=3D"http://www.postgresql.org/mailpref/pgsql= -bugs" target=3D_blank>http://www.postgresql.org/mailpref/pgsql-bugs<BR= >
В списке pgsql-bugs по дате отправления: