| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Tomasz Ostrowski <tometzky(at)batory(dot)org(dot)pl> |
| Cc: | 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 14:40:47 |
| Message-ID: | 20081016144046.GH4452@tamriel.snowman.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-performance |
* Tomasz Ostrowski (tometzky(at)batory(dot)org(dot)pl) wrote:
> There is an issue report with lengthy discussion on drupal.org:
> http://drupal.org/node/196862
> And a proposed patch:
> http://drupal.org/files/issues/drupal_lookup_path-5.x.patch.txt
> which uses "limit 1". This patch is not applied though. I don't know why.
I don't see 'limit 1' anywhere in that patch.. And you don't want to
use 'limit 1' *and* count(*), that doesn't do what you're expecting
(since count(*) is an aggregate and limit 1 is applied after). You
really want to do something more like:
select true from tab1 limit 1;
And then test if you got back any rows or not (which might be what
*your* patch does, hadn't looked at it yet).
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2008-10-16 14:43:19 | Re: PL/pgSQL stored procedure returning multiple result sets (SELECTs)? |
| Previous Message | Tom Lane | 2008-10-16 14:30:51 | Re: Numbering rows |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | DelGurth | 2008-10-16 15:09:44 | Re: Drupal and PostgreSQL - performance issues? |
| Previous Message | Tom Lane | 2008-10-16 14:29:44 | Re: further tests with 8.3 was: Re: Drupal and PostgreSQL - performance issues? |