From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: The query cache - first snapshot (long) |
Date: | 2000-07-27 03:36:07 |
Message-ID: | 200007270336.XAA12552@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> * PREPARE/EXECUTE
>
> - For tests I use query that not use some table (the executor is
> in boredom state), but is difficult for the parser. An example:
>
> SELECT 'a text ' || (10*10+(100^2))::text || ' next text ' || cast
> (date_part('year', timestamp 'now') AS text );
>
> - (10000 * this query):
>
> standard select: 54 sec
> via prepare/execute: 4 sec (93% better)
>
> IMHO it is nod bad.
>
> - For standard query like:
>
> SELECT u.usename, r.relname FROM pg_class r, pg_user u WHERE
> r.relowner = u.usesysid;
>
> it is with PREPARE/EXECUTE 10-20% faster.
>
>
> I will *very glad* if someone try and test patch; some discussion is wanted
> too.
Wow, just when I thought we couldnd't get much faster. That is great.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-07-27 03:43:16 | Re: Hello PL/Python |
Previous Message | Bruce Momjian | 2000-07-27 03:27:09 | Re: btree split logic is fragile in the presence of lar ge index items |