Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kN5rf-0003wz-SW for pgsql-admin@arkaria.postgresql.org; Tue, 29 Sep 2020 02:59:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kN5re-0003vK-OG for pgsql-admin@arkaria.postgresql.org; Tue, 29 Sep 2020 02:59:38 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kN5re-0003vD-AP for pgsql-admin@lists.postgresql.org; Tue, 29 Sep 2020 02:59:38 +0000 Received: from mail-pg1-x544.google.com ([2607:f8b0:4864:20::544]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kN5rb-0002Hq-Jy for pgsql-admin@lists.postgresql.org; Tue, 29 Sep 2020 02:59:37 +0000 Received: by mail-pg1-x544.google.com with SMTP id y14so2642960pgf.12 for ; Mon, 28 Sep 2020 19:59:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=86Wqpp8qWbEzgmcdxFO0o4xIo7mRfCxOkgQFZGRLozU=; b=pYRUNTs/EnR3bADK2VkBXfXP+Z2kibnhfl1X31ts6bRQDdg5mUcfJe7pgKN5GlY5ko VTWPO7dpupYOeh472FkbTAPxGib+h3ZFVMWdXkzy+bl3nzAcIEo8eN4mnkvWvZ7r3ISw E2bG20dGIOXC1WCxpNCEs94UtiEI5DDr9EfFb94XR316exsInWqbWjpMsTOmXjIGYGte WXcTSuOipQukl4rDoNpRZZmcKdL9ALr+305IcS4GNG3VAEwDITGD25Oq2/XaQH6W74pa X1hW8lEhrHGVg1fRAvhWphAYAt0wHhoUMUX+46xFvlSF/Am4n1thll+IEJnFZfIuJBtG Fc7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=86Wqpp8qWbEzgmcdxFO0o4xIo7mRfCxOkgQFZGRLozU=; b=YFHPN6szkXjM5u3rKmPQvu6/4gHu0OAZGy8hGbDr5t84fR0pkekoYCIpIhlyi18gCQ G/NLzSPzeKUP7cktbniR3+D/W3hHgVKEzqLEP8WGw2uFOQkYKEgfY+WbpzcIciT5oCLL 6FssRldF2KRWThge8QNm5OOItDlm4Ktu2TPfXW3tSwPnJ4TR4s47bITfMStQjQd9JP+p Uw1JXXesNAi3rDj8AKAmtowc3IBFM+G5OD1fJCREhUWzGSo3YFUr0kv1GZgOtOKFqFrG OeF+dCRFQb+CyGLNz8n5CEtXslkjpbjgMFdQyAkXYlQme/SsWRBe5ZI9KGMogyal874v 9iXQ== X-Gm-Message-State: AOAM530z19xFvzbxP8Jzg/H0q9DTcBnNqlv/NkLjq+lHNwB8rQVSqLf0 te5Q6YBRoFAMvzdxAy58Vh4dOJVVxj2CqKP3wN4= X-Google-Smtp-Source: ABdhPJwYF3B5QplkgFespEgaRVolzRwVQy8aLtA6aRrhpNbiuWW5A9l7r4h1JddPWoLycjHXaIc0m2BFna/0tqMTHTo= X-Received: by 2002:a17:902:7144:b029:d2:aa9a:843a with SMTP id u4-20020a1709027144b02900d2aa9a843amr633957plm.85.1601348374069; Mon, 28 Sep 2020 19:59:34 -0700 (PDT) MIME-Version: 1.0 References: <20200929021752.GA26860@momjian.us> In-Reply-To: <20200929021752.GA26860@momjian.us> From: Erik Serrano Date: Tue, 29 Sep 2020 00:02:02 -0300 Message-ID: Subject: Re: Upgrade 9.2 to 9.6 without modifying the location of the tablespaces To: Bruce Momjian Cc: pgsql-admin@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000ff863e05b06af82e" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000ff863e05b06af82e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thank you very much Bruce, I update the binary and the data in this way: bash# */usr/pgsql-9.6/bin/pg_upgrade* *--old-datadir /var/lib/pgsql/data/* *--new-datadir /var/lib/pgsql/9.6/data/* *--old-bindir /usr/bin/* *--new-bindir /usr/pgsql-9.6/bin/* And in that I would like to know if it is essential to move the data?. Remember that I do not have space on the disks to make a tablespaces move thank u Bruce *Erik R. Serrano Saavedra* El lun., 28 sept. 2020 a las 23:17, Bruce Momjian () escribi=C3=B3: > On Mon, Sep 28, 2020 at 11:17:39PM -0300, Erik Serrano wrote: > > Hello, I would like to know if there is any way to upgrade from a 9.2 t= o > 9.6 > > version without modifying the location of the tablespaces since I have > no more > > disks. > > Since one of the actions carried out within an upgrade is the creation > of new > > clusters and the movement of the data from the old location to the new > > location. > > > > Is it possible to perform? > > > > my server data is: > > Operating system: linux Red Hat 6.8 > > base size: 1101 GB > > discs : > > /dev/sdb1 1008G 713G 245G 75% /opt/data_postgres > > /dev/sdd1 512G 397G 90G 82% /opt/data_postgres2 > > > > Thank you very much in advance. > > Just move the tablespaces before or after the upgrade: > > https://momjian.us/main/blogs/pgblog/2018.html#October_3_2018 > > There is no way to move them during the upgrade. > > -- > Bruce Momjian https://momjian.us > EnterpriseDB https://enterprisedb.com > > The usefulness of a cup is in its emptiness, Bruce Lee > > --000000000000ff863e05b06af82e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thank you very much Bruce, I update the binary and th= e data in this way:

bash#= /usr/pgsql-9.6/bin/pg_up= grade --old-datadir /var/lib/pgsql/data/= = --new-datadir /var/lib/pgsql/9.6/data/--old-bindir /usr/b= in/ --new-bindir /usr/pgsql-9.6/bin/

=


And in that I would like to kn= ow if it is essential to move the data?. Remember that I do not have space = on the disks to make a tablespaces move
thank u=C2=A0 Bruce
=


Erik R. Serrano Saavedra=C2=A0= =C2=A0


El lun., 28 sep= t. 2020 a las 23:17, Bruce Momjian (<bruce@momjian.us>) escribi=C3=B3:
On Mon, Sep 28, 2020 at 11:17:39PM -0300, Erik Se= rrano wrote:
> Hello, I would like to know if there is any way to upgrade from a 9.2 = to 9.6
> version without modifying the location of the tablespaces since I have= no more
> disks.=C2=A0
> Since one of the actions carried out within an upgrade is the creation= of new
> clusters and the movement of the data from the old location to the new=
> location.
>
> Is it possible to perform?
>
> my server data is:
> Operating system: linux Red Hat 6.8
> base size: 1101 GB
> discs :
> /dev/sdb1=C2=A0 =C2=A0 =C2=A01008G=C2=A0 =C2=A0713G=C2=A0 =C2=A0 245G= =C2=A0 =C2=A075%=C2=A0 =C2=A0 /opt/data_postgres
> /dev/sdd1=C2=A0 =C2=A0 =C2=A0 =C2=A0512G=C2=A0 =C2=A0397G=C2=A0 =C2=A0= =C2=A0 90G=C2=A0 =C2=A082%=C2=A0 =C2=A0 /opt/data_postgres2
>
> Thank you very much in advance.

Just move the tablespaces before or after the upgrade:

=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://mom= jian.us/main/blogs/pgblog/2018.html#October_3_2018

There is no way to move them during the upgrade.

--
=C2=A0 Bruce Momjian=C2=A0 <bruce@momjian.us>=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://momjian.us=
=C2=A0 EnterpriseDB=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0https://enterprisedb.com=

=C2=A0 The usefulness of a cup is in its emptiness, Bruce Lee

--000000000000ff863e05b06af82e--