Subject: Re: reindexing db
To: pgsql-admin@lists.postgresql.org
References: <292966DF-135C-4483-81A9-5027FC3C8A82@elevated-dev.com>
 <f477709e-6371-1ba3-84df-37e5df8e5d83@gmail.com>
 <214E5DBC-1F6F-49C1-8B83-9A2EB33E969A@gmail.com>
From: Ron <ronljohnsonjr@gmail.com>
Message-ID: <39a8cdb5-bfbb-9ae8-5867-c4234373277c@gmail.com>
Date: Tue, 8 Dec 2020 00:59:08 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <214E5DBC-1F6F-49C1-8B83-9A2EB33E969A@gmail.com>
Content-Type: multipart/alternative;
 boundary="------------70B194933822BA67995F7BB7"
Content-Language: en-US
Precedence: bulk

This is a multi-part message in MIME format.
--------------70B194933822BA67995F7BB7
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

On 12/8/20 12:36 AM, Paul Förster wrote:
> Hi Ron,
>
>> On 08. Dec, 2020, at 06:42, Ron <ronljohnsonjr@gmail.com> wrote:
>>
>> Changing subjects, but the thought of reindexing every index, whether it needs it or not, in one command, seems like a crime against database administration.
> hmm, yes, I agree to *some* point. But also think about possible changes in glibc and the collation problems corrupting indexes that come with it. So, you do a reindexdb deliberately to protect yourself against index corruption because PostgreSQL can't know by itself that it needs such protection because it doesn't know of any changes in glibc.
>
> So, it's not a crime against database administration but rather a means of defense for a database administrator against an external crime attacking the database.

:)  I understand that sometimes all tables *need* to be reindexed.

Probably a habit from my VAX/VMS days, but I prefer to enumerate every 
table, not only for tracking but so that if the command fails 90% of the way 
through, I can skip over the the completed portions.

-- 
Angular momentum makes the world go 'round.

--------------70B194933822BA67995F7BB7
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    On 12/8/20 12:36 AM, Paul Förster wrote:<br>
    <blockquote type="cite"
      cite="mid:214E5DBC-1F6F-49C1-8B83-9A2EB33E969A@gmail.com">
      <pre class="moz-quote-pre" wrap="">Hi Ron,

</pre>
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">On 08. Dec, 2020, at 06:42, Ron <a class="moz-txt-link-rfc2396E" href="mailto:ronljohnsonjr@gmail.com">&lt;ronljohnsonjr@gmail.com&gt;</a> wrote:

Changing subjects, but the thought of reindexing every index, whether it needs it or not, in one command, seems like a crime against database administration.
</pre>
      </blockquote>
      <pre class="moz-quote-pre" wrap="">
hmm, yes, I agree to *some* point. But also think about possible changes in glibc and the collation problems corrupting indexes that come with it. So, you do a reindexdb deliberately to protect yourself against index corruption because PostgreSQL can't know by itself that it needs such protection because it doesn't know of any changes in glibc.

So, it's not a crime against database administration but rather a means of defense for a database administrator against an external crime attacking the database.</pre>
    </blockquote>
    <br>
    :)  I understand that sometimes all tables <b>need</b> to be
    reindexed.<br>
    <br>
    Probably a habit from my VAX/VMS days, but I prefer to enumerate
    every table, not only for tracking but so that if the command fails
    90% of the way through, I can skip over the the completed portions.<br>
    <br>
    <div class="moz-signature">-- <br>
      Angular momentum makes the world go 'round.</div>
  </body>
</html>

--------------70B194933822BA67995F7BB7--