From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Eric B(dot) Ridge" <ebr(at)tcdi(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: User Defined Functions/AM's inherently slow? |
Date: | 2004-01-19 03:59:15 |
Message-ID: | 20129.1074484755@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Eric B. Ridge" <ebr(at)tcdi(dot)com> writes:
> Wow, thanks for spending the time on this. What about for gettuple?
> Do calls to it take advantage of the cache? If not, this likely
> explains some of my custom am's performance troubles.
gettuple is looked up once at the start of a scan, so there's no
per-tuple overhead involved there. As I said before, we're usually
pretty good about avoiding per-tuple overheads --- the cost you
identified here is a per-query overhead.
> If there's anything I can do to help, let me know. I'll be happy to
> test any patches you might come up with too.
I have committed a patch into CVS HEAD --- give it a try.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | tim | 2004-01-19 07:54:03 | [patch] jdbc build fix when ./configure is run in separate dir |
Previous Message | Eric B.Ridge | 2004-01-19 03:20:46 | Re: User Defined Functions/AM's inherently slow? |