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 1lFLTl-0007Cu-Gi for pgsql-admin@arkaria.postgresql.org; Thu, 25 Feb 2021 18:35:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lFLTk-0005E3-DL for pgsql-admin@arkaria.postgresql.org; Thu, 25 Feb 2021 18:35:12 +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 1lFLTk-0005Dw-3L for pgsql-admin@lists.postgresql.org; Thu, 25 Feb 2021 18:35:12 +0000 Received: from mail-oo1-xc34.google.com ([2607:f8b0:4864:20::c34]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lFLTg-0005ci-RL for pgsql-admin@lists.postgresql.org; Thu, 25 Feb 2021 18:35:11 +0000 Received: by mail-oo1-xc34.google.com with SMTP id p6so1618123oot.2 for ; Thu, 25 Feb 2021 10:35:08 -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=AdSTU+iPRABIbs7b5Okhf6l9fUIlL/AguPGsCa6Az+0=; b=oyFOWZlbL5RTa6niX6/Porx79LRNxFoJQnb5dfQ6HqyC1QN2gLUa91zbA4ABHWbOvf EjVezsCEP7xTRaXTo58wXXmYOxHqLJ/OoTcfHuPS6jAkecVXL8uDs35DCvn8yNUKGan8 aSQN8Fs3b5tPaoeA2Vn1Rqdjt+Gt0r9W4s4Tj6kOVQtOWIVQItfgy3hL20jF8XyMhxqf Ib35Jt2MDBWKOOpO9MEvQgnB1LHUP9odz8WijiwklS/zYUvk+yiEXylqbBPnKNgLgQIm kMsLjQZT2GpTtiJ2NhT8XPzd80rABkkqpM070m9g65ebxVKtKQ+G36g4iqCNTaOsnZc8 DPiQ== 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=AdSTU+iPRABIbs7b5Okhf6l9fUIlL/AguPGsCa6Az+0=; b=SIbGooq6MbxHYWKU+uS0tCR4uuE4zsqs9ezX9BuOjIaWQ6J2GNlBw6fLCqAT9KQY5s B1cDpYkmpwozy/S8eR/UbC3tkLOCWpBUJpz9ynYY6t2zzoYY6EXL3E8okyBZKf5hKylZ PE6QlVBqAYt3ThjlS2u/V0zQ8AA79M9btGV/lE+HXXzhHfw6iIC4wyuRzouLKmVP7MXP rjHel8zqrhoQwSEPoyVlVeuDIhs3dUGqonr/TU3yZjAG1s8YY8ItCipiOGraxq988kfJ 25cnS0TJRS7UpukH0+QZDm8YenkqxdJ3pSBPvQcuRYBnv48y1Aw+TaC6LSTem+T4Y0Pb 72nw== X-Gm-Message-State: AOAM530m7ibB7fGiSYzj/dC/WN/fp+T8QogG35D9yhYj3UWTqzTtCv0z wDDlKV/BT5KHVngdZU9kUlYR/Kj+eFeR+A== X-Google-Smtp-Source: ABdhPJzk+ikYVrpB2FuHJBkNZ49nrMIFz+9cuiak6Tm8Cn+Ak6iMOYRW0kml0PR4pN/dv9Cto1T9qg== X-Received: by 2002:a4a:b387:: with SMTP id p7mr3436970ooo.82.1614278106505; Thu, 25 Feb 2021 10:35:06 -0800 (PST) Received: from [192.168.88.10] (ip174-67-141-204.no.no.cox.net. [174.67.141.204]) by smtp.googlemail.com with ESMTPSA id a25sm1297885oto.14.2021.02.25.10.35.05 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 25 Feb 2021 10:35:06 -0800 (PST) Subject: Re: Handling pg_toast tables To: pgsql-admin@lists.postgresql.org References: From: Ron Message-ID: Date: Thu, 25 Feb 2021 12:35:04 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2/25/21 5:40 AM, satish v wrote: > Hi, > > My table size is 15 MB but toast table size 92GB,i performed Vacuum and > vacuum full,but pg_toast table doesn't shrink.how can we shrink the > pg_toast table. If your database has many LARGE columns (bytea, xml, json or even long text values) then... that's how big the tables really are. -- Angular momentum makes the world go 'round.