From: | Matthias Apitz <guru(at)unixarea(dot)de> |
---|---|
To: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: REINDEX in tables |
Date: | 2023-10-25 09:57:30 |
Message-ID: | ZTjmivuUkIh7v6/u@pureos |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
El día miércoles, octubre 25, 2023 a las 11:33:11 +0200, Andreas Kretschmer escribió:
> 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.
But, this wasn't the question. It was: can it happen that the number of
rows in thze table will increase by this operation?
matthias
--
Matthias Apitz, ✉ guru(at)unixarea(dot)de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
I am not at war with Russia. Я не воюю с Россией.
Ich bin nicht im Krieg mit Russland.
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Kretschmer | 2023-10-25 09:59:38 | Re: REINDEX in tables |
Previous Message | Ron | 2023-10-25 09:35:46 | Re: setting up streaming replication, part 2 |