Skip site navigation (1) Skip section navigation (2)

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: (view raw, whole thread or download thread mbox)
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

pgsql-hackers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group