From: | Grzegorz Jaskiewicz <gj(at)pointblue(dot)com(dot)pl> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | David Fetter <david(at)fetter(dot)org>, pgsql-hackers Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: add_path optimization |
Date: | 2009-02-02 15:58:14 |
Message-ID: | D5866F3C-2275-4BFF-843E-624DD8202178@pointblue.com.pl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2 Feb 2009, at 14:50, Robert Haas wrote:
>> well, true - but also, statically allocated table, without any
>> predefined
>> size (with #DEFINE) , and no boundary check - is bad as well.
>> I suppose , this code is easy enough to let it be with your
>> changes, but I
>> would still call it not pretty.
>
> Well, it might merit a comment.
:)
>
> What I'd really like to do is develop some tests based on a publicly
> available dataset. Any suggestions?
I would say, it wouldn't hurt to do benchmarking/profiling regression
tests on real hardware - but someone will have to generate quite
substantial amount of data, so we could test it on small queries, up
to 20+ join/sort/window function/aggregation queries, with various
indexes, and data types. The more real the data, the better.
I could make some of my stuff public - but without the lookup tables
(id->some real data - like, names, surnames, mac addr, etc).
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2009-02-02 16:11:11 | Re: reloptions with a "namespace" |
Previous Message | Joshua Brindle | 2009-02-02 15:50:12 | Re: How to get SE-PostgreSQL acceptable |