Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1abyCb-0007FX-Q8 for pgsql-performance@arkaria.postgresql.org; Fri, 04 Mar 2016 22:28:05 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1abyCb-0006Ne-Bn for pgsql-performance@arkaria.postgresql.org; Fri, 04 Mar 2016 22:28:05 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1abyCa-0006NC-EZ for pgsql-performance@postgresql.org; Fri, 04 Mar 2016 22:28:04 +0000 Received: from mail-qg0-x231.google.com ([2607:f8b0:400d:c04::231]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1abyCX-0001q7-Pb for pgsql-performance@postgresql.org; Fri, 04 Mar 2016 22:28:03 +0000 Received: by mail-qg0-x231.google.com with SMTP id y89so55238301qge.2 for ; Fri, 04 Mar 2016 14:28:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=53jQGZ26QBq/k+aexGIO3zdVtneSKExrI+3h5PhwJK4=; b=0eIffZmTc5VWTfu/RE+snu9XZ6bSyy56VxMu0dsAdIaAEB/aTrTflvZaV4F8Jt9onX TN6fn6MOHIVy/Vp15Y4Ef/2ehVa3N25hYJ9CIlpyuIPCLaQVn1svkCUuZIm5vqnMlDs5 OwEUFVQaNnX499y66xfuJ+XHIkKV2cy4AJkCN/6vIdzpaOAI38WhQkiQ0kTcESQEB4If 6KK40pOF4UuHYfkWl9bYHy/PPDkmWWTG98zd/CVGCUibqvFFcciqEM+S4Vcx5mVaREKJ EGqLshpfhoG8acLQHmbWVRJUCLZLBU6uc3Ga2wcCkkTihaW/60ujVGM4c3NhsEM0BWvp mM+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=53jQGZ26QBq/k+aexGIO3zdVtneSKExrI+3h5PhwJK4=; b=Zv8VJ48r7KzeBSl7djjkHTdbXvNmmMGFbwGGVnYUd+589ba80Sct1NdJ28UGjqMmze 8MHyYqINPer9trWwLF62pXH6IKZF8SS6TAn+KByaZrjYDOAVcfy/DAzTbKPk24VBpP0q C+iczBKd6773mOEfmypGHT3acBOSxtZQd8jbaOJaJ83bs/82kyYtVpkmzH4KkyMxRpjt nXIqpx39IshSt5VG001PZAjkWlY6r7t/VOtx006zoX3E3FkRMG+c95t8G807aZs4hGRz fXwInEIpNT25bHVkAPHG6VwbvzGw4pc6nOwGZFEk986EFQqzAaKotqTCYZMNbD20J9S4 efSQ== X-Gm-Message-State: AD7BkJJhzbUpPXYk7Vf4aE90ud/VtbjvTpDJD8GK+Mtb5efwsse+Crk8cw+V9ws1TTadEBbh7MNCCJp/ZtmEBQ== MIME-Version: 1.0 X-Received: by 10.140.16.225 with SMTP id 88mr13454289qgb.96.1457130479974; Fri, 04 Mar 2016 14:27:59 -0800 (PST) Received: by 10.140.83.36 with HTTP; Fri, 4 Mar 2016 14:27:59 -0800 (PST) Date: Fri, 4 Mar 2016 14:27:59 -0800 Message-ID: Subject: Clarification on using pg_upgrade From: Tory M Blue To: "pgsql-performance@postgresql.org" Content-Type: multipart/alternative; boundary=001a11c0b3b4a69f72052d40a08f X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org --001a11c0b3b4a69f72052d40a08f Content-Type: text/plain; charset=UTF-8 Howdy Postgres9.2 going to 9.4 CentOS 6.5 So in most of my environments, I use slony and thus use slony replication for my upgrades (Drop/add nodes etc). But I've got a pretty big DB just shy of a TB that is on a single node. A dump restore would take over 48 hours because of index creations etc, so thought maybe I would look at doing a upgrade via pg_upgrade. There are some challenges, since I build my rpm's to a standard directory for binaries and then the data directory. So I will have to move/rename directories, but when that's done, I'm slightly confused on the pg_upgrade using link options. If my data is located in /data and I link to a new dir in /data1, what actually happens. do I end up with 2 file systems and links and thus am not able to delete or cleanup any old data, or how does this work? Also will the reindex creation still happen with this type of in-place upgrade, as if so, then it may not save too much time vs a dump/import. I'm nervous about using pg_upgrade but it's really tough to recover from the jobs that backup during a dump/restore process (2-3 days), so really trying to wrap my head around pg_upgrade.. Suggestions, opinions on pg_upgrade vs dump/restore, the filesystem/mount below is what I'm working with. Filesystem Size Used Avail Use% Mounted on /dev/sda6 4.0T 1.1T 2.8T 29% /data Thanks Tory --001a11c0b3b4a69f72052d40a08f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Howdy

Postgres9.2 going to 9.4
<= div class=3D"gmail_extra">CentOS 6.5
So in most of my environments, I use slo= ny and thus use slony replication for my upgrades (Drop/add nodes etc).

But I'= ;ve got a pretty big DB =C2=A0just shy of a TB that is on a single node. A = dump restore would take over 48 hours because of index creations etc, so th= ought maybe I would look at doing a upgrade via pg_upgrade.

There are some challe= nges, since I build my rpm's to a standard directory for binaries and t= hen the data directory. So I will have to move/rename directories, but when= that's done, I'm slightly confused on the pg_upgrade using link op= tions.

If my data is located in /data

<= div class=3D"gmail_extra">and I link to a new dir in /data1, =C2=A0what act= ually happens. do I end up with 2 file systems and links and thus am not ab= le to delete or cleanup any old data, or how does this work?

Also will the reinde= x creation still happen with this type of in-place upgrade, as if so, then = it may not save too much time vs a dump/import.

I'm nervous about using pg_up= grade but it's really tough to recover from the jobs that backup during= a dump/restore process (2-3 days), so really trying to wrap my head around= pg_upgrade..

Suggestions, opinions on pg_upgrade vs dump/restore, the filesystem= /mount below is what I'm working with.
=

Filesystem =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Size=C2=A0 Used Avail Use% Mo= unted on

/dev/sda6=C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 4.0T= =C2=A0 1.1T=C2=A0 2.8T=C2=A0 29% /data


Thanks
Tory
--001a11c0b3b4a69f72052d40a08f--