| From: | David Fetter <david(at)fetter(dot)org> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: add_path optimization |
| Date: | 2009-02-01 17:03:43 |
| Message-ID: | 20090201170343.GJ17601@fetter.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Jan 31, 2009 at 11:37:39PM -0500, Robert Haas wrote:
> I've been doing some benchmarking and profiling on the PostgreSQL
> query analyzer, and it seems that (at least for the sorts of queries
> that I typically run) the dominant cost is add_path(). I've been
> able to find two optimizations that seem to help significantly:
Are there any cases you've found where this change significantly
impairs performance, and if so, how did you find them? If not, would
you be up for trying to find some?
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-02-01 18:12:19 | Re: add_path optimization |
| Previous Message | Grzegorz Jaskiewicz | 2009-02-01 14:23:54 | Re: Updated backslash consistency patch |