Re: Accounting for toast in query planner. (gin/gist indexes).

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: jesper(at)krogh(dot)cc
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Accounting for toast in query planner. (gin/gist indexes).
Date: 2011-12-02 05:30:26
Message-ID: 6406.1322803826@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

jesper(at)krogh(dot)cc writes:
> Secondly I could bump the default cost of ts_match_vq/ts_match_qv a
> bit up, since the cost of doing that computation is probably not as
> cheap as a ordinary boolean function.

Actually, you could try bumping their costs up by more than "a bit".
It's a tad unfair to blame the toast access costs on the functions,
but it might get close enough to what you need. If memory serves,
we don't charge those costs against index scans.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2011-12-02 08:42:53 Re: Why so few built-in range types?
Previous Message Tom Lane 2011-12-02 05:16:08 Re: Inlining comparators as a performance optimisation