Am 25.10.23 um 11:24 schrieb Matthias Apitz:
> We have a client who run REINDEX in certain tables of the database of
> our application (on Linux with PostgreSQL 13.x):
>
> REINDEX TABLE CONCURRENTLY d83last;
> REINDEX TABLE CONCURRENTLY d86plz;
> REINDEX TABLE CONCURRENTLY ig_memtable;
> REINDEX TABLE CONCURRENTLY ig_dictionary;
> REINDEX TABLE CONCURRENTLY ig_dictionary;
> REINDEX TABLE CONCURRENTLY d50zweig ;
> REINDEX TABLE CONCURRENTLY d50zweig ;
>
> We as the software vendor and support, do not use or recommend this
> procedure, because we have own SQL files for creating or deleting
> indices in the around 400 tables.
>
> The client is now concerned about the issue that the number of
> rows in some of the above tables has increased. Is this possible?
In principle, there is nothing wrong with doing this in a maintenance
window, for example.
Regards, Andreas
--
Andreas Kretschmer - currently still (garden leave)
Technical Account Manager (TAM)
www.enterprisedb.com
