| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Andrus <kobruleht2(at)hot(dot)ee>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: How to use index in simple select |
| Date: | 2025-11-29 17:56:31 |
| Message-ID: | 8d872370-4d70-4398-b234-fe60a740032a@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 11/29/25 09:47, Andrus wrote:
> 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 ?
More likely it was one of the build index concurrently caveats detailed
here:
https://www.postgresql.org/docs/current/sql-createindex.html#SQL-CREATEINDEX-CONCURRENTLY
>
> Andrus.
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stuart Campbell | 2025-12-01 00:59:07 | Check whether a NOT NULL check constraint has been validated |
| Previous Message | Andrus | 2025-11-29 17:47:23 | Re: How to use index in simple select |