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.94.2) (envelope-from ) id 1qvadx-0066jA-NG for pgsql-general@arkaria.postgresql.org; Wed, 25 Oct 2023 09:57:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qvadv-001bGw-4b for pgsql-general@arkaria.postgresql.org; Wed, 25 Oct 2023 09:57:39 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qvadu-001bGo-PW for pgsql-general@lists.postgresql.org; Wed, 25 Oct 2023 09:57:38 +0000 Received: from ms-10.1blu.de ([178.254.4.101]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qvadr-002Dif-Lh for pgsql-general@lists.postgresql.org; Wed, 25 Oct 2023 09:57:37 +0000 Received: from [212.222.85.178] (helo=pureos) by ms-10.1blu.de with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1qvadn-007C4i-Up; Wed, 25 Oct 2023 11:57:31 +0200 Date: Wed, 25 Oct 2023 11:57:30 +0200 From: Matthias Apitz To: Andreas Kretschmer Cc: pgsql-general@lists.postgresql.org Subject: Re: REINDEX in tables Message-ID: Reply-To: Matthias Apitz References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Operating-System: FreeBSD 14.0-CURRENT 1400094 (amd64) X-message-flag: Mails containing HTML will not be read! Please send only plain text. X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 212.222.85.178 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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@unixarea.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.