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.96) (envelope-from ) id 1vgM3k-00BJEJ-2v for pgsql-bugs@arkaria.postgresql.org; Thu, 15 Jan 2026 12:02:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vgM2j-00Giso-1q for pgsql-bugs@arkaria.postgresql.org; Thu, 15 Jan 2026 12:01:37 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vgLzQ-00Giin-2G for pgsql-bugs@lists.postgresql.org; Thu, 15 Jan 2026 11:58:12 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vgLzO-000YgL-1S for pgsql-bugs@lists.postgresql.org; Thu, 15 Jan 2026 11:58:12 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=cYKEvnQGyO7l+AFrVM4bY6V+f+F4AmKoq4VPVVwfCzw=; b=J9xIsWMjaJ5XQBu6eoH32FNee/ 7qJm78wceQcyNgCSH2qK9K8kBdZ1wQ3wMGm/WnRaCiMdRZeO3XKUn46DD53Ea01pSd3AtKvB8vDhh 36Aiek1/Dgikp87juU+Vpunn3zhIQ6TNziBrrjFfogeCDo4OyFqAQGdAfiRwxl46lwcqugeQpB9mJ y/dI3shCkgH2XSdOnDQ6Usr+T+NXyVlwf+q674+EKL/zw6wQ5I+nyvUwoNpGhJpP3hzPgCHXOA5mx lyvjHKsOlYlkWCzVnI7mvlxPE/2htVfh/1nCJY9U3VyacqOIfXjKHrnZfZ8oyl/2xTYCOCbyR67V2 hAK0zRUg==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vgLzI-001ezT-0N for pgsql-bugs@lists.postgresql.org; Thu, 15 Jan 2026 11:58:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vgLzG-002p1N-2c for pgsql-bugs@lists.postgresql.org; Thu, 15 Jan 2026 11:58:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: BUG #19379: Role pg_read_all_data don't allowed read large objects To: pgsql-bugs@lists.postgresql.org From: PG Bug reporting form Cc: long76.git@mail.ru Reply-To: long76.git@mail.ru, pgsql-bugs@lists.postgresql.org Date: Thu, 15 Jan 2026 11:57:14 +0000 Message-ID: <19379-089536632927293f@postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following bug has been logged on the website: Bug reference: 19379 Logged by: Misha Shaygu Email address: long76.git@mail.ru PostgreSQL version: 17.7 Operating system: Kubuntu 24.04 Description: =20 My goal: create role for backup any database on server Steps: 1. CREATE USER backup_user; 2. GRANT pg_read_all_data TO backup_user; 3. pg_dump my_db 4. got error to read large object Following by links https://www.postgresql.org/docs/17/predefined-roles.html https://www.postgresql.org/docs/17/lo-implementation.html "SELECT privileges are required to read a large object" and role "pg_read_all_data" grant it, but it don't work! Please fix it, thanks!