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 1lFIGB-0007Bp-FB for pgsql-admin@arkaria.postgresql.org; Thu, 25 Feb 2021 15:08:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lFIGA-0002iQ-6P for pgsql-admin@arkaria.postgresql.org; Thu, 25 Feb 2021 15:08:58 +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 1lFIG9-0002iF-Pe for pgsql-admin@lists.postgresql.org; Thu, 25 Feb 2021 15:08:57 +0000 Received: from mail-ej1-x636.google.com ([2a00:1450:4864:20::636]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lFIG7-00023a-1O for pgsql-admin@postgresql.org; Thu, 25 Feb 2021 15:08:56 +0000 Received: by mail-ej1-x636.google.com with SMTP id a22so9410164ejv.9 for ; Thu, 25 Feb 2021 07:08:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=aABq6nEeVqx79UN9iClw4CHAw9BYIecyQvdoorxmPqw=; b=gqsZKAsC403QgnbMcg5snyNYwfxXuixugWONWytQEPUN85L28j8eiat8+vin8AQmzj sh/iM7hGjxDU5+2dhF++BL6gc4t6BNqqr60CDtxbSR4XAY0IqD8LhplTis9BahJqNmpI ajPmEQIfP1SKK8ph/QOGXEwB0RM3/OJyk2HfavpzB0EwSCjnu83TAvmm96QEsZQBjiNM PndOv48ivaroSgVp0ardT6ez24mnYDv2zyY0G/TrHAMFI3X15cJZ9huhwBkHj2s/Ukrz H5DrfM/+YOV/kXPeMxAz36WSmmocpb4Mc8Xhn09a6xOW9l3WDZtPKJnOWBQa0F2xE/PG MUuw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=aABq6nEeVqx79UN9iClw4CHAw9BYIecyQvdoorxmPqw=; b=MW+1EDxEZtlMHwo386VJM+FaFZVK4Wpm04Q1e557GCk6Igav3bPw1HV9bTtNvtAscT kpcCZ2CYqZ/EnT4FprHYCdcTgVWyOfTQ3ET3buxZQ81KhIHPGePiWqr8z9M7LPO9v6c5 l5vBpqJkkm8msIR7C+8ZDZuODcuB01RCZJ+NacNE7MyHj1DsCazY28T8E2qJ4WdImjm8 4Y+Nv6QWdgMr6ASiwE5t8VtgmD9Ka+KBPPyT1wn5ZagMsaN1LEQ7MNS1uDo9nzIMBrEJ ebFT0EuPia82+eYqAB2jGdyAGwM5GGrN/H6+RspLrB+gDVg5+FjWVr6VfIHVtqzJKCox bh8A== X-Gm-Message-State: AOAM533Vi4/nTMx3wBZ17ORutdzIbSBQ9x8jexd12qgKhhr8VZopDqNT aC0rQl2Jl/+388kuNmBty009FA== X-Google-Smtp-Source: ABdhPJz7rkWUAeFOwSA6MRTkHqREfY/b+hChbgy3HW40yEnqmfez3di4TUNEpNY6QONQb8kaVIl0Hg== X-Received: by 2002:a17:906:7d87:: with SMTP id v7mr3124316ejo.214.1614265733201; Thu, 25 Feb 2021 07:08:53 -0800 (PST) Received: from localhost.localdomain (217-149-170-47.nat.highway.telekom.at. [217.149.170.47]) by smtp.gmail.com with ESMTPSA id w2sm3804017edq.77.2021.02.25.07.08.52 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 25 Feb 2021 07:08:52 -0800 (PST) Message-ID: <50d73c5f33c7c2b0b9155186e4d4549e9fbd7613.camel@cybertec.at> Subject: Re: Handling pg_toast tables From: Laurenz Albe To: satish v , pgsql-admin@postgresql.org Date: Thu, 25 Feb 2021 16:08:51 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Thu, 2021-02-25 at 17:10 +0530, satish v wrote: > 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. Delete soe rows from the table? I guess there are some large attributes. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com