| From: | "Poul L(dot) Christiansen" <poulc(at)cs(dot)auc(dot)dk> |
|---|---|
| To: | KuroiNeko <evpopkov(at)carrier(dot)kiev(dot)ua> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Query caching |
| Date: | 2000-10-31 23:44:57 |
| Message-ID: | 39FF5979.C7677601@cs.auc.dk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
KuroiNeko wrote:
>
> > Here's a simple design that I was tossing back and forth. Please
> > understand that I'm not saying this is the best way to do it, or even a
> > good way to do it. Just a possible way to do it.
>
> Sounds interesting, I certainly have reasons to play bad guy, but that's
> what I always do, so nevermind :)
I think this feature deserves to be put on the TODO list under exotic
features.
This feature would probably also be a threat to MySQL dominance in the
web scripting area for websites with medium to high traffic ;)
Poul L. Christiansen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Kientzle | 2000-11-01 00:20:04 | Re: how good is PostgreSQL |
| Previous Message | KuroiNeko | 2000-10-31 23:07:01 | Re: Query caching |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mikheev, Vadim | 2000-10-31 23:45:17 | RE: WAL status update |
| Previous Message | Alfred Perlstein | 2000-10-31 23:11:44 | Query cache import? |