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 1vPc5w-008UE3-0b for pgsql-general@arkaria.postgresql.org; Sun, 30 Nov 2025 07:43:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vPc5t-00G76X-16 for pgsql-general@arkaria.postgresql.org; Sun, 30 Nov 2025 07:43:41 +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 1vPP2Z-00FFIa-2W for pgsql-general@lists.postgresql.org; Sat, 29 Nov 2025 17:47:24 +0000 Received: from smtpout05.dka.mailcore.net ([185.138.56.205]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vPP2Y-002CIb-0r for pgsql-general@postgresql.org; Sat, 29 Nov 2025 17:47:23 +0000 Received: from SMTP.DKA.mailcore.net (unknown [10.1.0.52]) by SMTPOUT01.DKA.mailcore.net (Postfix) with ESMTP id 89E5CE009E; Sat, 29 Nov 2025 18:47:21 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=online.ee; s=mailcore; t=1764438441; bh=koN9qwtf5A3NGJgRH6LVlCJNy5fFfR8QtPJFIHOyzmw=; h=Date:Subject:To:References:From:In-Reply-To:From; b=Ulj9Q6niuU76M5REaj1E6II4uwTAS4v1mMa871M4ap7bp1PaoGcq3qsIon1csbgPe K4Xb0jeHlk4Usanjuokxnp6OI+aR0YhF90hBdubZPEySHpBBk/c2ZbHB4c/w20D4Up ZvHGAdXBARJTmiZrkcH+7ZaLbLGrD9EZA3QxfaUeGh6HaGiXQfpoI4e4aPM6KLubTl jdmOZKVYmOpleR894E4FelOz2uUP8kvSdwAeuLIE1FsonUVw26gvqQvaKzH7N25aF9 YcKeMMJl1rk1S4m1sv/VWGanzQL9mZTD83tkkEjvV6Zti79hKo52kAFykTu4LOtL01 CDnpr2KUlK8rQ== Received: from [192.168.1.38] (73-142-35-213.sta.estpak.ee [213.35.142.73]) by SMTP.DKA.mailcore.net (Postfix) with ESMTPSA id 6B1A6400E7; Sat, 29 Nov 2025 18:47:21 +0100 (CET) Content-Type: multipart/alternative; boundary="------------rGE92X8iSOy4MW17cQwAz1Tl" Message-ID: <432c3538-e3b8-4e51-ad78-a30acddb5496@hot.ee> Date: Sat, 29 Nov 2025 19:47:23 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: How to use index in simple select To: Adrian Klaver , pgsql-general References: <3093741e-6a84-43e8-a009-fccff8abe998@aklaver.com> Content-Language: et From: Andrus In-Reply-To: <3093741e-6a84-43e8-a009-fccff8abe998@aklaver.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------rGE92X8iSOy4MW17cQwAz1Tl Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi! > Seems to be already answered: > > "It looks like reindex table firma2.klient restored index scan. create > index concurrently was used when lot of transactions using this table > where running" > Is it possible that reindex changes query from sequential scan to use index ? Andrus. --------------rGE92X8iSOy4MW17cQwAz1Tl Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

Hi!

Seems to be already answered:

"It looks like reindex table firma2.klient restored index scan. create index concurrently was used when lot of transactions using this table where running"

Is it possible that reindex changes query from sequential scan to use index ?

Andrus.

--------------rGE92X8iSOy4MW17cQwAz1Tl--