On Wed, Sep 30, 2009 at 4:13 PM, Robert Haas <robertmhaas@xxxxxxxxx> wrote: > On Wed, Sep 30, 2009 at 1:12 PM, Matthew Wakeling <matthew@xxxxxxxxxxx> wrote: >> >> Episode umpteen of the ongoing saga with my GiST indexes. >> >> For some reason, GiST uses loads of CPU. I have a query that runs entirely >> out of cache, and it takes ages. This much I have tried to fix and failed so >> far. >> >> What I would now like to do is to tell postgres about it, so that the >> EXPLAINs are correct. Is there a way to tell Postgres that an operator has a >> large CPU cost? I can tell it what the join selectivity is, but I can't find >> anything about CPU cost. > > Not that I know of, but seems like it would be a reasonable extension. Er, wait... if you set the 'COST' parameter for the backing function, does that work? . ...Robert -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
