| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | DelGurth <delgurth(at)gmail(dot)com>, "Tomasz Ostrowski" <tometzky(at)batory(dot)org(dot)pl>, "Mikkel H?gh" <mikkel(at)hoegh(dot)org>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Drupal and PostgreSQL - performance issues? |
| Date: | 2008-10-16 16:27:16 |
| Message-ID: | dcc563d10810160927t36806346kb42ccfc881d339bb@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-performance |
On Thu, Oct 16, 2008 at 9:26 AM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> * DelGurth (delgurth(at)gmail(dot)com) wrote:
>> Seems Tomasz linked to the wrong patch. The patch he meant was:
>> http://drupal.org/files/issues/drupal_lookup_path-6.x.patch.txt
>
> That's much better.
>
>> Also nice to see people "benchmark" differences by just executing a
>> query once[2][3]....
>
> This thread is insane.. Is every change to drupal run through this kind
> of design-by-committee? And the paranoia of a cost difference of 0.09ms
> for something which ends up getting cached for one particular storage
> engine under one particular database?!
>
> Makes me worried about drupal's future, heh.
In all fairness, pgsql goes through the same kind of design by
committee process. We just have a committee of very smart people
hashing things out.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2008-10-16 16:29:50 | Re: Problems with Timezones in Australia |
| Previous Message | Roderick A. Anderson | 2008-10-16 16:23:26 | Re: Problems with Timezones in Australia |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mikkel Høgh | 2008-10-16 21:17:35 | Re: Drupal and PostgreSQL - performance issues? |
| Previous Message | Stephen Frost | 2008-10-16 15:26:47 | Re: Drupal and PostgreSQL - performance issues? |