Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1glXxz-0002K5-Bf for pgsql-admin@arkaria.postgresql.org; Mon, 21 Jan 2019 11:42:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1glXxy-0004fN-1O for pgsql-admin@arkaria.postgresql.org; Mon, 21 Jan 2019 11:42:10 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1glXxx-0004f7-JF for pgsql-admin@lists.postgresql.org; Mon, 21 Jan 2019 11:42:09 +0000 Received: from mail-ot1-x342.google.com ([2607:f8b0:4864:20::342]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1glXxt-0004xC-Q5 for pgsql-admin@lists.postgresql.org; Mon, 21 Jan 2019 11:42:08 +0000 Received: by mail-ot1-x342.google.com with SMTP id a11so20225505otr.10 for ; Mon, 21 Jan 2019 03:42:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=EPpNzt71fQx9F+QcH8gVk2PbxI2TPWPJo7yACFt8hY4=; b=jYx/rKEJrsU3V3K098KCcKrctMSSikgCFOK1OXFrZ6T2TpB2H/1oSQG3cVkRA208AD DUaYn3udSqqx3bW6m15oJRKOEX26MC1vBiCItkUuY6/Ne44+rVMPto27GesoMc8aY2VJ SaZzOtFiqdmXl5D3Rt3FC1pJRxXP6dKdc3S7EFBeb6lpT4HgaKSgR81XChQ+QXlkCVjo pdL3GuBF/EtZ1KZ/gEEcE3yJL71wrt2Ix3ez/7V+o/oBrzM9ju301upPG2F+8qXGl1D6 dQX37UP8c2T3WujtOMKSCcW+CuBOWJyKonlSRkbKudxSW6ITvAvvzdHmCU1QeEyG2EyZ uuOQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=EPpNzt71fQx9F+QcH8gVk2PbxI2TPWPJo7yACFt8hY4=; b=i8csed2+XgBslHA6xCk73jSFzD7jol1TORU4r+zEeaozB3irvBzoW5+RVP4kxbROPv 0oq7HbkDWj4BaKja9TXip+kuLAj7mTgM1CZie8JOf9iRNMtZ+ieFi7N0k6bTQCVrPYQb 9SpUbswa9ce6OoFlJU9KVEiUCAxluHtmOj+v700V51q+QdVVwXAQ2lap9l5Ic0v9/p/m 832EfcbO1sPXLQGNIfSBd+xSZ+VslFn8Hlh6/SloKeqhujh1UyXLM4z1MSO03VLDu94e WxyvTQYv+5z1IomU4FWjWdRaHXTfxeIyv7bZvpUWjgUdETB7B47ezEZNbG/5qSD8kmqW lq4Q== X-Gm-Message-State: AJcUukdDzp1iy6DDWlXnWFq8Fxoxeel3mdYSqDnqJ5VjB/wSShGjmINr BoyDQtyU2PA4lEOF1cBjRF1ckZeC X-Google-Smtp-Source: ALg8bN4cf8C+VVZGFR6/yME9Zi3LOpY0ICnQ+wydw0JgDlAXwsyaZ5hWfJBjS7mqvOKNdcw2TKkeHQ== X-Received: by 2002:a9d:6a41:: with SMTP id h1mr19458405otn.332.1548070924176; Mon, 21 Jan 2019 03:42:04 -0800 (PST) Received: from [192.168.1.10] (ip70-171-116-89.no.no.cox.net. [70.171.116.89]) by smtp.googlemail.com with ESMTPSA id r9sm6032595otq.81.2019.01.21.03.42.02 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 21 Jan 2019 03:42:03 -0800 (PST) Subject: Re: Huge table pg_shdepend To: pgsql-admin@lists.postgresql.org References: <7ecdbaa3-07a6-1ec1-d991-06440c05b4cb@sourcepole.ch> From: Ron Message-ID: <728e7d92-4637-884f-eefb-fea50db46b6f@gmail.com> Date: Mon, 21 Jan 2019 05:42:02 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <7ecdbaa3-07a6-1ec1-d991-06440c05b4cb@sourcepole.ch> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 1/21/19 4:18 AM, Horst Düster wrote: > Hi > > I'm struggling with a huge table pg_shdepend. My database has a size of > 640MB exclude the size of the system tables. But the real size of the db > is more than 2GB. The reason is a huge table pg_shdepend with more than > 32000000 records.  PgAdmin3 shows a table size of > 1885MB and an index size of 1690MB. This looks strange for me, because > this size is a multiple amount of the db size itself. I believe, that > there are a lot of rubbish in that table, but I'm not sure. > > I had run a vacuum full process, but this didn't help. Could anyone give > me an advice how to clean the table pg_shdepend or reduce the table size? Silly question: did you vacuum the postgres database, or your user database(s)? Also, you should do the "vacuumdb --freeze --dbname=postgres" when nothing else is attached to any databases, so that nothing else can be holding old records in that table. -- Angular momentum makes the world go 'round.