Re: Index trouble with 8.3b4 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Index trouble with 8.3b4
Date
Msg-id 24770.1199845983@sss.pgh.pa.us
Whole thread Raw
In response to Re: Index trouble with 8.3b4  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
Gregory Stark <stark@enterprisedb.com> writes:
> "Tom Lane" <tgl@sss.pgh.pa.us> writes:
>> Now an unindexed dead tuple is not a problem from vacuum's point of
>> view, nor does ANALYZE care, so AFAICS there is no need for this step
>> to wait for autovacuum processes --- nor indeed for manual vacuums.

> Also, ANALYZE was included in the latest security changes. Is there some way
> that ANALYZE could trigger some user-defined function being invoked which
> could in turn run some SQL using this index?

Hmm.  ANALYZE itself doesn't look into the indexes, but it does invoke
user-defined functions that could nominally run queries.  However, a
function in an index that runs a query that examines its own table seems
implausible, and very unlikely to work right anyway.  You could hardly
expect such a function to be really immutable -- consider for example
that it would be unlikely to deliver the same results during CREATE
INDEX on an already-filled table that it would if the rows were being
inserted with the index already existing.  So I'm not really worried
about that scenario.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Gregory Stark
Date:
Subject: Re: Named vs Unnamed Partitions
Next
From: Alvaro Herrera
Date:
Subject: Re: Index trouble with 8.3b4