At 10:38 AM 8/01/2004 +1100, you wrote:

>I noted that the processor goes on 100% every time I select * from a view,
>with a filter, filtering on fields without an index.

What you are seeing is *probably* the first query on an underlying table
that has received large updates in a previous transaction - it will catch
the garbage collection from that previous transaction.

What happens if you wait until that query finishes fetching, commit the
transaction and run the same query again?

/heLen