| From: | Frank Joerdens <frank(at)joerdens(dot)de> |
|---|---|
| To: | Elielson Fontanezi <ElielsonF(at)prodam(dot)sp(dot)gov(dot)br> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: RES: PHP + PostgreSQL |
| Date: | 2002-09-20 09:20:53 |
| Message-ID: | 20020920112053.B12784@superfly.archi-me-des.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Sep 20, 2002 at 10:53:24AM +0200, Frank Joerdens wrote:
[ . . . ]
> SELECTs are usually not hard to do
> fast anyway because especially with web apps, you'd want to have some
> kind of caching mechanism.
I put that really badly: What I was trying to say is that for web
applications in most scenarios, the select performance of the database
itself is not as crucial as some people seem to think. This is because
you're not going to get very far without some caching mechanism anyway,
and if you have a caching mechanism, it depends on how well the system
is implemented. All these benchmarks pertaining to the select
performance of the sql database behind your Apache/PHP app really put
you on the wrong track altogether. It's not how it works.
Mind you, this is still very general, and those are sweeping statements.
It all depends.
Regards, Frank
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yury Bokhoncovich | 2002-09-20 10:10:57 | Re: missed features and unhappy changes when pg 7.1->7.2 |
| Previous Message | Richard Huxton | 2002-09-20 09:15:13 | Re: BYTEA |