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 1qvcjy-006HsJ-5D for pgsql-general@arkaria.postgresql.org; Wed, 25 Oct 2023 12:12:02 +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 1qvcjv-0034nR-RE for pgsql-general@arkaria.postgresql.org; Wed, 25 Oct 2023 12:11:59 +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 1qvcjv-0034mV-CH for pgsql-general@lists.postgresql.org; Wed, 25 Oct 2023 12:11:59 +0000 Received: from mail-ej1-x631.google.com ([2a00:1450:4864:20::631]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qvcjo-002Ekq-2v for pgsql-general@lists.postgresql.org; Wed, 25 Oct 2023 12:11:57 +0000 Received: by mail-ej1-x631.google.com with SMTP id a640c23a62f3a-9adb9fa7200so175242166b.0 for ; Wed, 25 Oct 2023 05:11:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20230601.gappssmtp.com; s=20230601; t=1698235910; x=1698840710; darn=lists.postgresql.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:from:to:cc:subject :date:message-id:reply-to; bh=aNGhjZaDxc8oX9TVk51FEkL+4nKOCCBE9nB3nTMcwCU=; b=ozR/3OlGgfwIlLUPtUSawZMkrgOoUu3+pfH/AysEL+6QhMbk/NTy6y79qZHie26Nsi FOdyDolhFGh17HVIEMgaNvrShrDCZfaKE4FuS59E9I3ZMC3V+cG0UtnBp4Bpt4UOLlPm 9kpIOLYd68bJNN2ERJ8+6Aj+/u6UKe5SQagq7hH2aoJTJlCWMEGibaxRZ8faaJUIYmBX f00f7Q72sRe5W+vfUIhuQ/NQogWj3N2EN4e/wsrA/plJK96ap2F9txMG7wPe1uPrWjL1 rNn9Y0JS6Aq0/6LXNABukY+mrYHE1gRXmjU19luar1ZN7ZoTp8yb0+N8byCAW+RUaNzJ g4vg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698235910; x=1698840710; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=aNGhjZaDxc8oX9TVk51FEkL+4nKOCCBE9nB3nTMcwCU=; b=biwqy0SbZgZYzVFn85miS19hQlUQISA9AI2YQNxrFh4TCzmA8BCj/zFIYL3rqfMXvS 8HL4iDkle1GZunGqeeDsY+Zld3f5918jnOCmm83L7Fd9Lr7BB735Dv79QFKjPonbhYQD /dSZ3niXvNfzO+b/sqPRwiD2jBLJ98rti9g8CZT7gNvyzReVWNXtpFK6luGHnVZhN9GV kXfyKq2tGUkArsLk8JUvSrya1lJ9oeyYZozvBeJprc+hbJ7a46XeO9bi7BF+4XRAtqP2 MeiI/Xnqjzlx08NfLmOr1WQ8hoicBkBwkzCyFuB0eIy9fA6Bohk7vrSLZF3uK9KrS6Sk c2tw== X-Gm-Message-State: AOJu0Yy/0Xwn8/K47eMyW3s5Lx4kbYoUVbviXZQRHYLh3QalOFE04HRI Hu7N6vQeSFrkIglRCMLI2F5/kQ== X-Google-Smtp-Source: AGHT+IHeZ36BwJ+tFeKXf3dPba7TkGUTjsna3yVJ4QHDY2vXOPMcj0/gchN2Gzk0De8X2jFd5+1mEA== X-Received: by 2002:a17:907:9620:b0:9b2:be2f:e31a with SMTP id gb32-20020a170907962000b009b2be2fe31amr15695141ejc.31.1698235910363; Wed, 25 Oct 2023 05:11:50 -0700 (PDT) Received: from localhost.localdomain ([2001:871:5e:51bf:5b1f:6a5d:5dcf:8bdd]) by smtp.gmail.com with ESMTPSA id g17-20020a17090613d100b009a1a653770bsm9641163ejc.87.2023.10.25.05.11.49 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 25 Oct 2023 05:11:50 -0700 (PDT) Message-ID: Subject: Re: REINDEX in tables From: Laurenz Albe To: Andreas Kretschmer , Matthias Apitz Cc: pgsql-general@lists.postgresql.org Date: Wed, 25 Oct 2023 14:11:49 +0200 In-Reply-To: <2786bf60-266d-8f82-2dee-4a43b90e16bb@a-kretschmer.de> References: <2786bf60-266d-8f82-2dee-4a43b90e16bb@a-kretschmer.de> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, 2023-10-25 at 11:59 +0200, Andreas Kretschmer wrote: > Am 25.10.23 um 11:57 schrieb Matthias Apitz: > > El d=C3=ADa mi=C3=A9rcoles, octubre 25, 2023 a las 11:33:11 +0200, Andr= eas Kretschmer escribi=C3=B3: > > > 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): > > > >=20 > > > > 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 ; > > > >=20 > > > > 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. > > > >=20 > > > > The client is now concerned about the issue that the number of > > > > rows in some of the above tables has increased. Is this possible? > >=20 >=20 > no, reindex will not add rows to the table. But if the indexes were corrupted before the REINDEX, it is possible that a query that didn't find a result before the REINDEX can find one afterward= s. Yours, Laurenz Albe