Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qMX01-002chU-AX for pgsql-admin@arkaria.postgresql.org; Thu, 20 Jul 2023 16:59:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qMWzz-00CPgQ-N0 for pgsql-admin@arkaria.postgresql.org; Thu, 20 Jul 2023 16:59:31 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qMWzz-00CPgG-By for pgsql-admin@lists.postgresql.org; Thu, 20 Jul 2023 16:59:31 +0000 Received: from mail-yw1-x112b.google.com ([2607:f8b0:4864:20::112b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qMWzv-000gc5-JB for pgsql-admin@lists.postgresql.org; Thu, 20 Jul 2023 16:59:30 +0000 Received: by mail-yw1-x112b.google.com with SMTP id 00721157ae682-579e212668fso16034367b3.1 for ; Thu, 20 Jul 2023 09:59:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1689872366; x=1690477166; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=ZZ23XSy0+k1ETvFbyuQwH/IEQXBdJPRIKaOAyiUhg7Q=; b=sKx+u9+dAyHCmlrFmiPffasy5x5onJbfg8uMxOXIuXb+STXomsJJDuuGzlQeAxe5Kx 3WJTj5u25/xGrlNN7wP0S1UjcgZTiqk86EG/dTfHaoWv41SxgTXONO558jfHBsvbrCZO ojorUAi7T/XpsqMjziK5iVpvR28dTeDNOAUSZ5p+fU2CDkbLD7fn8DZ9s6iIXzI7QotQ c/bvLgRMhXP66AoyvNaMthv9SrHYIT60sCFDuypL4Gs5YweE3MXnSdapzpkm9CPXbyj+ dH6ZBO9K+hhgOdiJKooq1Y1O4apm/9A0h5kP8eeXg3sqH3VNVfkcg2DdaNKDpbb5SJf/ uASA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689872366; x=1690477166; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=ZZ23XSy0+k1ETvFbyuQwH/IEQXBdJPRIKaOAyiUhg7Q=; b=Ic917IN730G032o1mtk4zuXiJ8wum7wvEViA7zQMIm27jRBT++C9QK7uMgjAyxjzvs 6rf+6h/Gw/ZjA0KvtnILnGZe/OAsiHXPdQwgOfDFs3/26jg+b0XJWOjTmTjNFZzhcKeH /A1FykSzKETXSo/+1pThRa+qmg2p8zycuGvVoif1+vWt8MCntkhdMLKc96jeQGq8D/ft jQALLNscYjS1S2loSjiTxMdZVB404MHd+uR19vDUVm/HmqTaGrqH8KVlWAAdbkKOin0s R+tfdseesr6wGDyBKGVIBhiJdQzEb0/6QQKXstUqnQeodO46fcpEFIhHjlzaBXyuZA0l 7XKQ== X-Gm-Message-State: ABy/qLaH2B/fzC0G+alMy3BhxfbHNGdLXw+SlAlw94cMfBXsiYH9YQgY meFJAgWnMEzuSzp9Xe11N2zNbUj9SbY= X-Google-Smtp-Source: APBJJlHgwsActzvylrSep0aIGT8EUpSdODbgmNobRRk1QczjhAqPqYIP2ambBIIRV/QeN2NMR+oPfA== X-Received: by 2002:a0d:cc4a:0:b0:57a:8ba5:224b with SMTP id o71-20020a0dcc4a000000b0057a8ba5224bmr6161524ywd.9.1689872366577; Thu, 20 Jul 2023 09:59:26 -0700 (PDT) Received: from ?IPV6:2600:1700:bd2c:b810:64d0:3aec:6103:5398? ([2600:1700:bd2c:b810:64d0:3aec:6103:5398]) by smtp.googlemail.com with ESMTPSA id x203-20020a8163d4000000b00573a75cd331sm303037ywb.143.2023.07.20.09.59.26 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 20 Jul 2023 09:59:26 -0700 (PDT) Message-ID: <9502f877-c699-4f28-4bb3-4cd3753c14da@gmail.com> Date: Thu, 20 Jul 2023 11:59:25 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: Upgrade from PG12 to PG Content-Language: en-US To: pgsql-admin@lists.postgresql.org References: <3901e0da-819b-5b6d-bb57-c29f6d384725@gmail.com> From: Ron In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Don't use pg_dumpall.  Use this instead: pg_dump --format=directory --jobs=X --verbose On 7/20/23 08:46, Jef Mortelle wrote: > Hi, > > Many thanks for your answer. > > So: not possible to have very little downtime if you have a database with > al lot rows containing text  as datatype, as pg_upgrade needs 12hr for 24 > milj rows in pg_largeobject. > > Testing now with pg_dumpall en pg_restore .... > > > I think, postgresql should take this in high priority to  resolve this > problem. > > I have to make a choice in the near future: Postgres or Oracle, and that > database would have a lot of datatype text. > Database would have 1 TB. > It seems me a little bit tricky/dangerous to use Postgres, just for being > able to upgrade to a newer version. > > Kind regards. > > On 20/07/2023 13:43, Ilya Kosmodemiansky wrote: >> Hi Jef, >> >> >> On Thu, Jul 20, 2023 at 1:23 PM Jef Mortelle wrote: >>> Looking at the dump file: man many lines like SELECT >>> pg_catalog.lo_unlink('100000'); >>> >>> >>> I have the same issue with /usr/lib/postgresql15/bin/pg_upgrade -v -p >>> 5431 -P 5432 -k >>> >>> >>> Whats going on ? >> pg_upgrade is known to be problematic with large objects. >> Please take a look here to start with: >> https://www.postgresql.org/message-id/20210309200819.GO2021%40telsasoft.com >> >>> >>> Kind regards >>> >>> >>> > > -- Born in Arizona, moved to Babylonia.