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 1pVZfm-00010R-61 for pgsql-admin@arkaria.postgresql.org; Fri, 24 Feb 2023 15:07:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pVZfk-0006Wb-TG for pgsql-admin@arkaria.postgresql.org; Fri, 24 Feb 2023 15:07:44 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pVZfk-0006WJ-Eb for pgsql-admin@lists.postgresql.org; Fri, 24 Feb 2023 15:07:44 +0000 Received: from mail-qt1-x82f.google.com ([2607:f8b0:4864:20::82f]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pVZfh-0002V6-Qk for pgsql-admin@lists.postgresql.org; Fri, 24 Feb 2023 15:07:43 +0000 Received: by mail-qt1-x82f.google.com with SMTP id r5so4922033qtp.4 for ; Fri, 24 Feb 2023 07:07:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:from:content-language:references:to:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=eYOpKehtFagJBvxW4+fGtR4bNAhWXciKmK9aBo994e4=; b=e8hxl3GlqZnPTxqsOIWpUMSkq3Q7f481GrRhKfAlsv/NdGZj/mAs8lO2QAfqeKW24V l1yQV8M4TuNWlSaLyQz5etggjMxrETnbme2PwpoaYTaQCRQZahp/Ay+WvvoueXEwPxFg STzEBiTbCZ2Iqj/PgA5j5FP0ytLc4fX1S4BgEM8LG/flCTVI/yog/uPS4YWLKtC6zc7w s5ROLKDeKydD7Q5o3DS5MqB+stf68oyopZLFJKZxolTY+rUIZV6NEixfJio1i1VC3vrP QT0UKDfghmakeedf6tfW4Mv+0s1Y/CItg+QLNv4KFAO7KnlpQqtNYmKdQ2iY7VlMz8aN jPkw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:from:content-language:references:to:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=eYOpKehtFagJBvxW4+fGtR4bNAhWXciKmK9aBo994e4=; b=WKUPf+MTtsfqdky5ZPy3353P3frZwmDE2mK72/BR9Dx0EwXuOu495SpiNpUiqiJ10F s3gRQDRDCkrjtbNLU9B2OBldEObPjmZNQ6IYQs96RahL2pJF2w76/6JhXYVRkZIL5Hh1 NmgFInOx01fqP5ce2S+ENEHxHfbaae+UUxkOokNfZnnGoaqsAu90km+SaD4rY7+imkV5 F8RIn+07lGHf/io6QxcrOL6cudy9m+ziwhjVtLpI3CG9/CFrQ/VJyNYuZpVAZIzYoBcg 17o0V9R8TBHUhzPGl2V1/uNOGdryi5WA93LgxYR9N1xqrckCl0LkkHISQELtHSDNwMDz 1W9A== X-Gm-Message-State: AO0yUKX9VmOho8Df2ed/jEueE9UBca/R2rESQncM28yXmJ/tFnN3T2/y sOd/ax4z2/sbNvIK9Rhq29IjsLrw0R8= X-Google-Smtp-Source: AK7set+6tPvjkT7Xj0XyWXAUZ92MVsFwIc1vVdfbFdto9y9tHWufA6OnQyYN9BZglIn5ecEF9Uxi8w== X-Received: by 2002:a05:622a:13ce:b0:3ba:38:2f59 with SMTP id p14-20020a05622a13ce00b003ba00382f59mr15576300qtk.2.1677251259116; Fri, 24 Feb 2023 07:07:39 -0800 (PST) Received: from ?IPV6:2600:1700:bd2c:b810::43? ([2600:1700:bd2c:b810::43]) by smtp.googlemail.com with ESMTPSA id c27-20020ac81e9b000000b003bfbfd9a4aesm695861qtm.56.2023.02.24.07.07.38 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 24 Feb 2023 07:07:38 -0800 (PST) Content-Type: multipart/alternative; boundary="------------aWpCm40xZd0ICcv2NymNlmyi" Message-ID: Date: Fri, 24 Feb 2023 09:07:38 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: pg_dump: error: could not open large object To: pgsql-admin@lists.postgresql.org References: Content-Language: en-US From: Ron In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------aWpCm40xZd0ICcv2NymNlmyi Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit "permission denied" is a pretty good place to start researching. On 2/24/23 08:58, Ankur Kaushik wrote: > While taking backup we are getting below issue, Please help for this issue > > pg_dump --username=postgres > --host=db-progresql-nvirgina.us-east-1.rds.amazonaws.com >  --port=5432 dbname > > > pg_dump: error: could not open large object 3628599: ERROR:  permission > denied for large object 3628599 > > > Posgresql version : 14.3 > > > On Fri, Feb 24, 2023 at 8:25 PM Ankur Kaushik wrote: > > > While taking backup we are getting below issue, Please help for this issue > > pg_dump --username=postgres > --host=db-progresql-nvirgina.us-east-1.rds.amazonaws.com > --port=5432 > dbname > > > pg_dump: error: could not open large object 3628599: ERROR:permission > denied for large object 3628599 > -- Born in Arizona, moved to Babylonia. --------------aWpCm40xZd0ICcv2NymNlmyi Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit "permission denied" is a pretty good place to start researching.

On 2/24/23 08:58, Ankur Kaushik wrote:
While taking backup we are getting below issue, Please help for this issue

pg_dump --username=postgres --host=db-progresql-nvirgina.us-east-1.rds.amazonaws.com --port=5432 dbname


pg_dump: error: could not open large object 3628599: ERROR:  permission denied for large object 3628599


Posgresql version : 14.3


On Fri, Feb 24, 2023 at 8:25 PM Ankur Kaushik <ankurkaushik@gmail.com> wrote:

While taking backup we are getting below issue, Please help for this issue

pg_dump --username=postgres --host=db-progresql-nvirgina.us-east-1.rds.amazonaws.com --port=5432 dbname


pg_dump: error: could not open large object 3628599: ERROR:  permission denied for large object 3628599


--
Born in Arizona, moved to Babylonia.
--------------aWpCm40xZd0ICcv2NymNlmyi--