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 1nfsPe-00018U-FA for pgsql-admin@arkaria.postgresql.org; Sun, 17 Apr 2022 00:05:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nfsPb-0006rp-Pw for pgsql-admin@arkaria.postgresql.org; Sun, 17 Apr 2022 00:05:07 +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 1nfsPb-0006rg-CV for pgsql-admin@lists.postgresql.org; Sun, 17 Apr 2022 00:05:07 +0000 Received: from mail-ej1-x62d.google.com ([2a00:1450:4864:20::62d]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nfsPU-0004uL-Nq for pgsql-admin@lists.postgresql.org; Sun, 17 Apr 2022 00:05:06 +0000 Received: by mail-ej1-x62d.google.com with SMTP id s18so21378101ejr.0 for ; Sat, 16 Apr 2022 17:05:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20210112.gappssmtp.com; s=20210112; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=SRW6HX8GwmY+EAZeAEN5foVc8d6SFiREub9nppxIaQk=; b=26/i1qRcpqSBmzGzpSHHC6bF4WCIn69GXa7adQ06CqQhRqRpK0q7iCYoVyV9nfo9FB 6P8d+tVSVl01ri+ZPrFcOoQG9vFNH5j5wBnTmAwQbJ+gsQ/+I21KvHKnkMNXQA5kFoBm /0AzFqoIPKj1W8RglNB1eRbxnXDbT55p5RU2zcGlWQblGYXV/OjK+xBdbkzf+nrjYX+q aHtANRfdiQL+kr5YqwNCtaEzFw8v+jKVvkSH9UpKaNl6lKYtOFIdm9iJQ/toTy3TgpuY cAnJujH2bO3hUjT8S9zKP9fKxk7NfY69rqnNgJV2RDeO1oxPN68Pxa+0m59h31X3bYIn vKlw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=SRW6HX8GwmY+EAZeAEN5foVc8d6SFiREub9nppxIaQk=; b=BYc90db32GtlRcQ56lLB3pbsDSdmoHB+zNmx0hxu8vKHMoiIicW4hMR7T0ED3av4kn equ33l6WhqEHKAAB3tiXpQAXxPnUtvwbVjUSmqBhejf4DPwDhl15iKp5Eqtc71vU8if5 U+iDwLt3Ho27wNgBxWXMp6dWFwVb7j8JpkQfNN6F5mY/8EgUdYP06YC2EBk6DhfLjg3+ 7pA8yEkN7G0/Ou+mOY0qgyMHbL6LUIF/iXn//hnOqznTS94D5YZRRRh4NmOJrelMxGW2 xn6SqUQ074yRkZFfHxKc6bajp44nBVIv10UoxDSegZgxVWoT5W/nRH0Ow5IoY3cnYyjS g2VA== X-Gm-Message-State: AOAM532nck349/AXyJe+gt9v2wAphQma5/41/34iiiRWHpx0BAn5qHB1 4bC3kyOmjcaUVI96N47y2zGDpQ== X-Google-Smtp-Source: ABdhPJxp3QiCBYh4ZGbVjpvQjVInGnAjkgoDPfxbTD/7QPSdi4RL7r5EXABk39pXGgCUzfjFvJ+HXQ== X-Received: by 2002:a17:907:8a03:b0:6ec:8197:e8ac with SMTP id sc3-20020a1709078a0300b006ec8197e8acmr3957180ejc.379.1650153899173; Sat, 16 Apr 2022 17:04:59 -0700 (PDT) Received: from localhost.localdomain (62-47-145-91.adsl.highway.telekom.at. [62.47.145.91]) by smtp.gmail.com with ESMTPSA id s14-20020aa7cb0e000000b00410bf015567sm4763449edt.92.2022.04.16.17.04.58 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 16 Apr 2022 17:04:58 -0700 (PDT) Message-ID: Subject: Re: PostgreSQL LO From: Laurenz Albe To: liam saffioti , pgsql-admin Date: Sun, 17 Apr 2022 02:04:57 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.40.4 (3.40.4-3.fc34) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sat, 2022-04-16 at 13:07 +0300, liam saffioti wrote: > I wonder about the large objects in postgresql. I have a database in PostgreSQL 12 > and there are many large object records in pg_largeobjects. But I don't know how it > was created. Also, I guess all large objects are orphaned because they will be > removed when I run vacuumlo command with the dry run option on the database. > > How do I find out the reason for how these large objects were created? > > Also, I don't have any binary data on the database tables. You'll have to ask the people who created and used the database. Yours, Laurenz Albe