Re: using index "pg_toast_..." despite IgnoreSystemIndexes

Hi

We use standalone mode because we have found that (anecdotally) it
completes faster.

We do the procedure because it's a scripted operation on servers of
different point releases and its easier to always do it than to
code for which ones need and which ones don't - same script every
time (and we also reindex in a separate step)

Thanks

On Tue, 28 Aug 2012 12:24:51 -0400 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
wrote:
>lsq(at)nym(dot)hush(dot)com writes:
>> After an upgrade to 8.4.12 from 8.4.10 we vacuum/analyzed the
>db.
>> Postgres is running in standalone mode at this point.
>
>Why were you using standalone mode? And why were you using
>ignore_system_indexes? This whole procedure seems like overkill
>for a routine minor-version update.
>
>> 07/31/12 04:09:57 WARNING: using index "pg_toast_2619_index"
>
>> despite IgnoreSystemIndexes
>
>> I see the warning generated in systable_beginscan_ordered as a
>> warning, and then it proceeds to do the work anyway.
>> It appears as if this is benign. Is that the case?
>
>It is unless you have some reason to think that that index is
>corrupt...
>
> regards, tom lane