Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WpA88-0005kn-Rg for pgsql-admin@arkaria.postgresql.org; Tue, 27 May 2014 05:40:57 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WpA87-00049N-6v for pgsql-admin@arkaria.postgresql.org; Tue, 27 May 2014 05:40:55 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1WpA84-00049E-VM for pgsql-admin@postgresql.org; Tue, 27 May 2014 05:40:53 +0000 Received: from nm38.bullet.mail.ne1.yahoo.com ([98.138.229.31]) by magus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1WpA7z-00057U-03 for pgsql-admin@postgresql.org; Tue, 27 May 2014 05:40:51 +0000 Received: from [127.0.0.1] by nm38.bullet.mail.ne1.yahoo.com with NNFMP; 27 May 2014 05:40:43 -0000 Received: from [98.138.101.132] by nm38.bullet.mail.ne1.yahoo.com with NNFMP; 27 May 2014 05:37:46 -0000 Received: from [106.10.166.123] by tm20.bullet.mail.ne1.yahoo.com with NNFMP; 27 May 2014 05:37:45 -0000 Received: from [106.10.151.234] by tm12.bullet.mail.sg3.yahoo.com with NNFMP; 27 May 2014 05:37:28 -0000 Received: from [127.0.0.1] by omp1018.mail.sg3.yahoo.com with NNFMP; 27 May 2014 05:37:45 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 446753.1290.bm@omp1018.mail.sg3.yahoo.com Received: (qmail 33229 invoked by uid 60001); 27 May 2014 05:37:45 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.in; s=s1024; t=1401169065; bh=6V3MZi96+PpoTk32nck9JdXqoG/2xYO0/jxwwNBf7QY=; h=References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=oRNkR8+uilo3qt3fBmAtY2G+BoDd/w2ZhPglfDXgozZKi9x/u5H/Qq6XncCiXgjg5/wR+LralhKupSB4cvcPntQTWQXNW3k29mFNIC8YRaqNo6X/eyw4SX9U515mn2m0pDnhDcOipLKlgKQhiNfa6klgMgWl4stCR7fp89oubic= X-YMail-OSG: FiOTmjoVM1nM5HYSXHHc4Z8KjchE6hkzLVAkjbVHpeJuVad 7Xo3Z_99_FLeoiwgARFRFgEVgbwbSRw0iHhb4y9DP5XZ24YcTGun85zm3TIm iQRO_XHNEW1CqSFE0k4w6xy_3v_JMQVSk_uYABzTbW2J2V_ZkTDaiAXqvqpD EHiGE_5UlnadSE21APOgyu_0UhBSRJT6BA2lm.XmsK9vgTyAE0LXdll9_IAO FavxF9uWKqkCxKm22cq1s.sUOt5V1YN3zYMzmg.tHKRYSnv6KyT.oW8pWu7O FKxM.5msDbsDFKM8RNkh_XM.ER0UGixxINtjRLFnfemnl9FkNFsMJl.8zJe5 vao.xMjcPN_o.W1xQgYpTcxSdfTFSWUwo5qutzHcaLIPW6Oeid.ZQ6c1VjbR D8es7WTn73.5GOwN.zCaO.TGqMtxJU8gAFAmDqLU2XNXIDBSVntI3h0gA3WJ uodRQwNn3yhOfvsHh0QnOx9pYqDaft8UlWF6WxoX91WbV9.SsutKBINcTgXz 8xq9tywA6YXY6u_SZq_ZxOw8Ws1DCLDYsUdy.E5Q8Q8d_f9kOZ8zsBrc9jds - Received: from [218.248.37.146] by web190804.mail.sg3.yahoo.com via HTTP; Tue, 27 May 2014 13:37:45 SGT X-Rocket-MIMEInfo: 002.001, VXNlIHBlcmwgNS4xNCBvciBsYXRlciB2ZXJzaW9uIGZvciBtaWdyYXRpbmcgZnJvbSBwb3N0Z3JlcyA5LjEgdG8gcG9zdGdyZXMgOS4zLgoKUmVnYXJkcwpPbSBQcmFrYXNoCgoKCgpPbiBNb25kYXksIDI2IE1heSAyMDE0IDg6MTggUE0sIEx1aXMgPGx1aXNpY29AZ21haWwuY29tPiB3cm90ZToKIAoKCk9rLCBzb3JyeSBmb3IgdGhlIG5vaXNlLiBJIGhhZCBhIGVycm9yIGluIG15IHVwZ3JhZGUgc2NyaXB0LCBhbmQgaXQKd2FzIG5vdCBiZWluZyByZWFsbHkgaG9ub3JlZC4KTm93IGl0IHdvcmtlZC4KCkhvd2UBMAEBAQE- X-Mailer: YahooMailWebService/0.8.188.663 References: Message-ID: <1401169065.22048.YahooMailNeo@web190804.mail.sg3.yahoo.com> Date: Tue, 27 May 2014 13:37:45 +0800 (SGT) From: om prash jaiswal Reply-To: om prash jaiswal Subject: Re: Doubt about pg_upgrade with link mode To: Luis , "pgsql-admin@postgresql.org" In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="1490027246-1621458396-1401169065=:22048" X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org --1490027246-1621458396-1401169065=:22048 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Use perl 5.14 or later version for migrating from postgres 9.1 to postgres = 9.3.=0A=0ARegards=0AOm Prakash=0A=0A=0A=0A=0AOn Monday, 26 May 2014 8:18 PM= , Luis wrote:=0A =0A=0A=0AOk, sorry for the noise. I ha= d a error in my upgrade script, and it=0Awas not being really honored.=0ANo= w it worked.=0A=0AHowever it still would be great being able to read some a= rticle or=0Adocumentation that details a little bit information about the l= ink=0Amode.=0A=0ACheers=0A=0A=0A2014-05-26 16:37 GMT+02:00 Luis :=0A> Hi,=0A>=0A> I'm trying to upgrade a PG 9.1 cluster to a 9.3 o= ne.=0A> I'm trying to use --link to do it in link mode since I don't have m= uch=0A> disk space for the migration.=0A>=0A> I'm not totally sure that the= --link parameter is being honored. I=0A> can't see any mention about link = mode in the migration logs and the=0A> new cluster takes too much space.=0A= >=0A> I would like to understand how link mode really works. What does it= =0A> link and what does it copy. Unfortunately I didn't find information=0A= > about that. Any link that provides more info would be appreciated.=0A>=0A= > I've compare inodes from base files in the old data directory and the=0A>= new one and they are different.=0A>=0A> copying "/9.1/base/18976/74003" to= "/9.3/base/16416/73829"=0A>=0A> $ stat /mnt/pg_data/base/18976/74001 --pri= ntf=3D%i=0A> 12454860=0A>=0A> $ stat /mnt/pg_data-9.3/base/16416/73829 --pr= intf=3D%i=0A> 10488427=0A>=0A> It doesn't seem to be a hard link. Should it= ?=0A=0A=0A-- =0ASent via pgsql-admin mailing list (pgsql-admin@postgresql.o= rg)=0ATo make changes to your subscription:=0Ahttp://www.postgresql.org/mai= lpref/pgsql-admin --1490027246-1621458396-1401169065=:22048 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Use perl 5= .14 or later version for migrating from postgres 9.1 to postgres 9.3.

Regards
Om Prakash


On Monday, 26 May 2014 8:18 PM, Luis <luisico@gm= ail.com> wrote:


Ok, sorry for the noise. I had a error in my upgrade script, and it
was not being really honored.
Now it worke= d.

However it still would be great bei= ng able to read some article or
documentation that detail= s a little bit information about the link
mode.

Cheers

2014-05-26 16:37 GMT+02:00 Lui= s <lui= sico@gmail.com>:
> Hi,
>> I'm trying to upgrade a PG 9.1 cluster to a 9.3 one.<= br clear=3D"none">> I'm trying to use --link to do it in link mode since= I don't have much
> disk space for the migration.
>
> I'm not totally sure that the --= link parameter is being honored. I
> can't see any men= tion about link mode in the migration logs and the
> n= ew cluster takes too much space.
>
&= gt; I would like to understand how link mode really works. What does it
> link and what does it copy. Unfortunately I didn't find= information
> about that. Any link that provides more= info would be appreciated.
>
> I= 've compare inodes from base files in the old data directory and the
> new on= e and they are different.
>
> cop= ying "/9.1/base/18976/74003" to "/9.3/base/16416/73829"
&= gt;
> $ stat /mnt/pg_data/base/18976/74001 --printf=3D= %i
> 12454860
>
> $ stat /mnt/pg_data-9.3/base/16416/73829 --printf=3D%i
> 10488427
>
> It doesn't = seem to be a hard link. Should it?

--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin


--1490027246-1621458396-1401169065=:22048--