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 1q6Aeq-0001Pg-Vv for pgsql-admin@arkaria.postgresql.org; Mon, 05 Jun 2023 13:54:05 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q6Aep-0008G8-K9 for pgsql-admin@arkaria.postgresql.org; Mon, 05 Jun 2023 13:54:03 +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 1q6Aep-0008El-3x for pgsql-admin@lists.postgresql.org; Mon, 05 Jun 2023 13:54:03 +0000 Received: from mail-ed1-x536.google.com ([2a00:1450:4864:20::536]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1q6Aej-000Nyb-HL for pgsql-admin@lists.postgresql.org; Mon, 05 Jun 2023 13:54:02 +0000 Received: by mail-ed1-x536.google.com with SMTP id 4fb4d7f45d1cf-5148e4a2f17so7421380a12.1 for ; Mon, 05 Jun 2023 06:53:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20221208.gappssmtp.com; s=20221208; t=1685973237; x=1688565237; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:from:to:cc:subject:date :message-id:reply-to; bh=vvyNJzuPpJd3BPFAGvpgkXF87YbhOpCrUf/eBuJxo9w=; b=Zx+ia4Bk/7dmBpsfDfERDkhWrsB+7Is3fMcm6X1wL9+AZI7NPRHJD7vx60zbOdPMRh ZNH97aSRWzC4xqfUimrY8pJPPlEEWBvVDkMRpN87/d23Lh0awfbpH1GUSx+lXYJBDvqI sbBpQXUoLybExm3aQqpChECIC/uoDH/qLhQPNOfFFi7wukor209tB7fyvw/nPnCzKuum hrvGjzN9o2eB56kBSxaTKFTLw9WS/OV23F9cCbbOythIMH1MGPVBjD5GIhS5BNgiueER eatIQEGxwBzZwYiA/qdAsZnAnVgzFDs8abVrHcK3FPa8zWY7wESZotbvZCQ6L1jI0iba H66g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685973237; x=1688565237; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=vvyNJzuPpJd3BPFAGvpgkXF87YbhOpCrUf/eBuJxo9w=; b=O940PeblmHHI8DMQ3+AMdNSzpXZkHHya3x8gYH6mSEWJ5EyviBAkH6qFPlIyK23oUS aqiRV5dXeq+G0GLE8DGE9wLvKHI86Jcp5mx21sMjmOv8J7MWDttlaXfAcLOF0HxuNtQm etHEKR9lT3ow6CcteyDCXgRWSuqQvHH47dnYLrzb86LXrzLYU99aESwmXTXTIbqmY1tH uD11N9jM5E3pxJo2+ANyJCklThirBEEf6tNkP/Ffxb6LRLaxMgsbU1Y+L8z0XVoSZ1YG cG51LpmtM1RiD/KAcW26lxS0saqHEX4nxBllyceFCmW3TI/06DvCf8R1kxUREDh423nZ a8cw== X-Gm-Message-State: AC+VfDznIQgiQ6qWJsWLlv0M1ZgJh3SSFizIfZe2/+aZ7+jUWisoAjhC wyTTepAh3iptx+AzSzstt4v5gg== X-Google-Smtp-Source: ACHHUZ7UDDCAkYqI8Y4GF3k+jj7XjTIbsRu90z7HKtPFHxb+z649CvTvuv2TIjYjhoDpNmrpbMyLow== X-Received: by 2002:aa7:da42:0:b0:50d:f9b1:6918 with SMTP id w2-20020aa7da42000000b0050df9b16918mr7677981eds.9.1685973236757; Mon, 05 Jun 2023 06:53:56 -0700 (PDT) Received: from localhost.localdomain ([2001:871:5e:6888:bdff:4d5b:3b36:4e7b]) by smtp.gmail.com with ESMTPSA id n23-20020aa7c797000000b005027d31615dsm3868820eds.62.2023.06.05.06.53.56 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 05 Jun 2023 06:53:56 -0700 (PDT) Message-ID: <9a869f91ea1eb760fb38c144ccad2f747bc68e38.camel@cybertec.at> Subject: Re: Error while exporting large objects. From: Laurenz Albe To: "Singh, Gambhir" , "pgsql-admin@lists.postgresql.org" Date: Mon, 05 Jun 2023 15:53:55 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.46.4 (3.46.4-1.fc37) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, 2023-06-05 at 11:44 +0000, Singh, Gambhir wrote: > > While exporting the large objects getting error mentioned below. I=E2= =80=99m trying to take export on Aurora PostgreSQL. > > > > pg_dump: error: could not open large object 28534: ERROR:=C2=A0 permiss= ion denied for large object 28534 > > Please provide some update on this. This is showstopper in my prod env. You have to use a database user that has the required permission. Connect with "psql" and run \lo_list+ 28534 to see the permissions on the large object. Yours, Laurenz Albe