| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Naz Gassiep <naz(at)mira(dot)net> |
| Cc: | Hannes Dorbath <light(at)theendofthetunnel(dot)de>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: In theory question |
| Date: | 2007-05-09 17:29:02 |
| Message-ID: | 464204DE.2050906@commandprompt.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Naz Gassiep wrote:
> Hannes Dorbath wrote:
>> I think this is close to what MySQL's query cache does. The question
>> is if this should be the job of the DBMS and not another layer. At
>> least the pgmemcache author and I think that it's better done outside
>> the DBMS. See
>> http://people.FreeBSD.org/~seanc/pgmemcache/pgmemcache.pdf for the idea.
> This is exactly what I was asking about. So my theoretical idea has
> already been implemented. Now if only *all* my ideas were done for me by
> the time I came up with them :)
Then you wouldn't be able to eventually patent them ;)
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Naz Gassiep | 2007-05-09 17:52:12 | Re: In theory question |
| Previous Message | Naz Gassiep | 2007-05-09 17:19:44 | Re: In theory question |