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 1mhP2c-0006Cd-QK for pgsql-admin@arkaria.postgresql.org; Mon, 01 Nov 2021 04:35:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mhP2b-0005lD-8R for pgsql-admin@arkaria.postgresql.org; Mon, 01 Nov 2021 04:35:25 +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 1mhP2a-0005jF-Qn for pgsql-admin@lists.postgresql.org; Mon, 01 Nov 2021 04:35:24 +0000 Received: from mail-wm1-x32a.google.com ([2a00:1450:4864:20::32a]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mhP2T-0007Vg-OV for pgsql-admin@postgresql.org; Mon, 01 Nov 2021 04:35:23 +0000 Received: by mail-wm1-x32a.google.com with SMTP id 77-20020a1c0450000000b0033123de3425so1208352wme.0 for ; Sun, 31 Oct 2021 21:35:17 -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=u+jtxMVYUZWpO/2dEoc4uowEemo+/bzcl9/Wa5lAaHQ=; b=BUmNMxe5ruVnUMJ3Qn+6xSL/hSO9MeNEVbrATSN1Z/ADaPmFYwLa5AyTl4C48fogPM M5zjAYVntMcPTQt4soaUCLONhOyWOUiOcFaKBVahqtC+pir2b7cH9/+Mgxq7YmU6VO3f gqzEZ8+fTIWn7AqcCiKQ63RTj6BHaY008rZpj+UZhrSD2WzvN517EaHiHzV1o+AH59b1 qNKRBIx4VRdZ/+cUs6ShRFLt/njou10SIca0/mhP+S5xvC7TRC4BakHWAt0ORy3Mdiar gXzPCk/RqvtU6U7hKKejNo7HIu01/W+nLZ3YD4wk0HAVoQKoocTuhydHs1I2SNwXXbWU TF7g== 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=u+jtxMVYUZWpO/2dEoc4uowEemo+/bzcl9/Wa5lAaHQ=; b=SyVkRCzyUqUAT0uYJCR602VZfvo0IMBCp25qfZlqQtY3F+OOGQ8A0PxUmpAZJfkjhQ nfiBMdCrs6Gsf43vmiYFbsDdoD0XAOKlcUd8WfzU6+vygco76y1AQ8zKPn3Av0eRv8XW pO1vGTDVcmRyq+C+M2ZbpXTEsvsiY40yMvM8Il26iT/HWE+jEcWC3Mei8qhcS2rWSgWI AvL5hURgPo5RFRSWeFVXkfMf0L7ywLnZzQAo3bpxlNRVp3wGxREbPFcoAERXZ6kDDlwN iM91PtKP0U1voiOCKijBRY1+U50s9t7i0cMe+dyyyOaIgMIiYnkpZW1H5b2is+nljlpq Wd9Q== X-Gm-Message-State: AOAM531gsUypfIwhMyRZ65GqLm5thAukOtEkpXr9CBoo6Sti0eydQgir H6yESnc4ACQdYeEqISZrw/HtpQ== X-Google-Smtp-Source: ABdhPJwexn3twvtKn4RXPSR2p7xmp0pjlnviHIGzgJ6yV9CAStnWI+gAePF3GQfSc7V3OcSsLCjlxA== X-Received: by 2002:a05:600c:4fd1:: with SMTP id o17mr37049866wmq.110.1635741315303; Sun, 31 Oct 2021 21:35:15 -0700 (PDT) Received: from localhost.localdomain (62-47-151-123.adsl.highway.telekom.at. [62.47.151.123]) by smtp.gmail.com with ESMTPSA id z6sm4489441wrm.93.2021.10.31.21.35.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 31 Oct 2021 21:35:15 -0700 (PDT) Message-ID: Subject: Re: Know bloat percentage after auto vacuum From: Laurenz Albe To: satish v , pgsql-admin@postgresql.org Date: Mon, 01 Nov 2021 05:35:14 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.40.4 (3.40.4-2.fc34) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sat, 2021-10-30 at 21:33 +0530, satish v wrote: > We have the table with 2 months data (approx 450GB). We deleted 17 days of data and auto vacuum > performed on the table.new insertions are utilizing  that space,we want to perform the vacuum full > and reclaim the space at os level but don't know how much free (unused) space available.how can we get the details. CREATE EXTENSION pgstattuple; SELECT tuple_percent, dead_tuple_percent, free_percent FROM pgstattuple('table_name'); Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com