Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vgRax-00CrIR-2H for pgsql-general@arkaria.postgresql.org; Thu, 15 Jan 2026 17:57:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vgRaw-0010zc-1s for pgsql-general@arkaria.postgresql.org; Thu, 15 Jan 2026 17:57:18 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vgRav-0010zP-2E for pgsql-general@lists.postgresql.org; Thu, 15 Jan 2026 17:57:18 +0000 Received: from fout-b2-smtp.messagingengine.com ([202.12.124.145]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vgRas-000fBU-3A for pgsql-general@postgresql.org; Thu, 15 Jan 2026 17:57:17 +0000 Received: from phl-compute-06.internal (phl-compute-06.internal [10.202.2.46]) by mailfout.stl.internal (Postfix) with ESMTP id 4D0041D0007D; Thu, 15 Jan 2026 12:57:12 -0500 (EST) Received: from phl-frontend-04 ([10.202.2.163]) by phl-compute-06.internal (MEProxy); Thu, 15 Jan 2026 12:57:12 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm1; t=1768499832; x=1768586232; bh=tUgsqLt64HsTVzmW3IDP51B+J1hVaLrwwGU6nF7Bxqc=; b= dyT1mYGyZFptTInwruOgAcfKm2q7tVhQVanuv5cSSBqzTgyHHJHXGPinH7CapV6+ ACEc1HazLDn/fL2LW8pvhxDMRD3P2zMutglUkIjVV1NUZ+xRTYJFYvVC1vvhKCpQ VFqrPWu0i2xb/qmnzj3lE71EjLqul722Sw1YAlhDNIJv2XoUY0X81kSAAr1wZlI9 4r8bgipqPX2zvlTWDuEMvomu5h9ocL9yXGIPEAFTaP7jytWAC8SbdYkN/K+lM4yl LJwEjq+zerppDdeuLTbgU7fqIRGuECwhbqRiAGLYxVBgCaUsP8RXg+53nxF78NId ryeFlaF4MSEVMLCDPY2FSA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1768499832; x= 1768586232; bh=tUgsqLt64HsTVzmW3IDP51B+J1hVaLrwwGU6nF7Bxqc=; b=u C9InwLUS2p15ndPsqW1372UeiCBoQ0hr+laMyoc7pWhGqFd6VLzyc7UTuCX2OYIW fEj7q2U9AwXZ820s2S65UrPikmmIDXBSZETHWXKh3wjdoKePQ4AYZHjmBjtfkdTq QK2r08K85Pt5dwqBZVxvhXSb+wShAS4BEssVTpXA+J9u0WjQd5ZZjCNYxOpnCYA8 Fo3te2CYk23e8jKXpqpwXFS4gN/NCyDVOQojNS4sHBuYolKhmTEwBhPNr6R2/rKG 6nR33IxU9h7+gGDhWFUBsl5xAP58zDSkphvzZnpGjFEGotKX8WhVds9vrHCthWbQ 9jrN51VfyJIg78QxQpwDg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefgedrtddtgdduvdeijeduucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfhfvefhjggtgfesthejre dttddvjeenucfhrhhomheptegurhhirghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhl rghvvghrsegrkhhlrghvvghrrdgtohhmqeenucggtffrrghtthgvrhhnpefgtdekteehud etgfeghfevheeftdeffeevueejudehiedtleekheffudefkefftdenucffohhmrghinhep ghhithhhuhgsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomhdpnhgs pghrtghpthhtohepvddpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepmhgrihhlvd hsohhnhidvtddutdesghhmrghilhdrtghomhdprhgtphhtthhopehpghhsqhhlqdhgvghn vghrrghlsehpohhsthhgrhgvshhqlhdrohhrgh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 15 Jan 2026 12:57:11 -0500 (EST) Message-ID: <722db7f0-2d89-48ef-8f0f-9ae4191d5817@aklaver.com> Date: Thu, 15 Jan 2026 09:57:11 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: How did VACUUM ANALYZE reclaim large TOAST bloat at disk level in PostgreSQL 16? To: pramod gupta References: <7ae94444-a4cd-45da-b8c8-308cd46fc391@aklaver.com> Content-Language: en-US Cc: pgsql-general From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 1/15/26 09:48, pramod gupta wrote: Again, you need to use Reply All to get post to mailing list Ccinglist. You did not answer 2) or 3). Though the below is revealing: > postgres@ANRPGTEST01:~$ ls -ltrh /var/lib/postgresql/.pg_ai.config > -rw------- 1 postgres postgres 1.8K Jan 15 17:03 /var/lib/ > postgresql/.pg_ai.config > postgres@ANRPGTEST01:~$ pwd > /var/lib/postgresql > postgres@ANRPGTEST01:~$ psql > psql (16.11 (Ubuntu 16.11-1.pgdg24.04+1)) > Type "help" for help. > > postgres=# \q Per: https://github.com/benodiwal/pg_ai_query/issues/38 " benodiwal last month Thanks for sharing, actually .pg_ai.config should be in your home directory and not root. Can u try to put it in home directory once and they try. sudheermudunuri same with me as well i added in /var/lib/postgresql/.pg_ai.config but still it doesn't load from the config file. benodiwal Hey @sudheermudunuri, it is designed this way in first release. Can u please try putting it in home dir. " -- Adrian Klaver adrian.klaver@aklaver.com