Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dYEfP-000281-PA for pgsql-admin@arkaria.postgresql.org; Thu, 20 Jul 2017 16:51:11 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dYEfP-0005Uk-8q for pgsql-admin@arkaria.postgresql.org; Thu, 20 Jul 2017 16:51:11 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dYEfO-0005UK-He for pgsql-admin@postgresql.org; Thu, 20 Jul 2017 16:51:10 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dYEfH-0008G1-VL for pgsql-admin@postgresql.org; Thu, 20 Jul 2017 16:51:09 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v6KGoudq005953; Thu, 20 Jul 2017 12:50:56 -0400 From: Tom Lane To: =?UTF-8?B?0K/QvdGH0LXQvdC60L4g0JLQu9Cw0LTQuNC80LjRgA==?= cc: pgsql-admin@postgresql.org Subject: Re: Strange size of pg_largeobject In-reply-to: References: Comments: In-reply-to =?UTF-8?B?0K/QvdGH0LXQvdC60L4g0JLQu9Cw0LTQuNC80LjRgA==?= message dated "Thu, 20 Jul 2017 20:59:12 +0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <5951.1500569456.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Thu, 20 Jul 2017 12:50:56 -0400 Message-ID: <5952.1500569456@sss.pgh.pa.us> List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org =3D?UTF-8?B?0K/QvdGH0LXQvdC60L4g0JLQu9Cw0LTQuNC80LjRgA=3D=3D?=3D writes: > I found that my pg_largeobject table is bigger than it should be: Sounds like a fairly routine case of table bloat. > Before I execute queries, that i mentioned above, I run vacuum full. But= =20 > it does not effect. Now table bloating factor about 20%. "vacuum verbose pg_largeobject" might be informative. If, as I suspect, it tells you there are lots of dead but unremovable rows, look around for long-lived open transactions or prepared transactions. regards, tom lane --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin