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
[email protected]
