pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Andreas Kretschmer <andreas@a-kretschmer.de>
To: Matthias Apitz <guru@unixarea.de>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: REINDEX in tables
Date: Wed, 25 Oct 2023 14:11:49 +0200
Message-ID: <bedf2448c1a2a14f476a2abadd0a3034065df7dc.camel@cybertec.at> (raw)
In-Reply-To: <2786bf60-266d-8f82-2dee-4a43b90e16bb@a-kretschmer.de>
References: <ZTjesqtUit3mwDXt@pureos>
	<aa6471fb-f709-9574-246a-f3531453b638@a-kretschmer.de>
	<ZTjmivuUkIh7v6/u@pureos>
	<2786bf60-266d-8f82-2dee-4a43b90e16bb@a-kretschmer.de>

On Wed, 2023-10-25 at 11:59 +0200, Andreas Kretschmer wrote:
> Am 25.10.23 um 11:57 schrieb Matthias Apitz:
> > 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?
> > 
> 
> 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 afterwards.

Yours,
Laurenz Albe





view thread (8+ messages)  latest in thread

Message-ID: <bedf2448c1a2a14f476a2abadd0a3034065df7dc.camel@cybertec.at>
Permalink:  ../bedf2448c1a2a14f476a2abadd0a3034065df7dc.camel@cybertec.at/
Also on:    postgresql.org/message-id/bedf2448c1a2a14f476a2abadd0a3034065df7dc.camel@cybertec.at

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: laurenz.albe@cybertec.at, andreas@a-kretschmer.de, guru@unixarea.de
  Subject: Re: REINDEX in tables
  In-Reply-To: <bedf2448c1a2a14f476a2abadd0a3034065df7dc.camel@cybertec.at>
  References: <ZTjesqtUit3mwDXt@pureos> <aa6471fb-f709-9574-246a-f3531453b638@a-kretschmer.de> <ZTjmivuUkIh7v6/u@pureos> <2786bf60-266d-8f82-2dee-4a43b90e16bb@a-kretschmer.de> <bedf2448c1a2a14f476a2abadd0a3034065df7dc.camel@cybertec.at>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox