pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tomasz Ostrowski <tometzky@batory.org.pl>
To: Mikkel H?gh <mikkel@hoegh.org>
Cc: pgsql-general <pgsql-general@postgresql.org>
Subject: Re: Drupal and PostgreSQL - performance issues?
Date: Thu, 16 Oct 2008 10:54:47 +0200
Message-ID: <48F70157.7010601@batory.org.pl> (raw)
In-Reply-To: <4BE94DFB-8917-4175-9083-7DEABC30BD7F@hoegh.org>
References: <a93e6cbe-0000-4000-9a34-4db3620c619d@mm>
	<C6449FCD-198D-4A04-BACB-1BB2F20DD5B1@hoegh.org>
	<48F4F053.1060201@hagander.net>
	<F933F17A-70BC-4DB0-9491-9EEF0E79ABD9@hoegh.org>
	<b42b73150810141422i5ad693a8la3966fa6334c23f7@mail.gmail.com>
	<7438A981-4B6A-4E5A-A1E0-50432CDEFB00@hoegh.org>
	<48F6EE94.8010904@batory.org.pl>
	<4BE94DFB-8917-4175-9083-7DEABC30BD7F@hoegh.org>

On 2008-10-16 10:34, Mikkel Hogh wrote:

> It's not only to avoid one query, but to avoid one query every time  
> drupal_lookup_path() is called (which is every time the system builds  
> a link, which can be dozens of time on a page).

Oh, $count is static. My bad. Using count for testing for empty table is
stupid nonetheless.

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.

Please retest with this patch. And keep the CC to the list in your messages.

Regards
Tometzky
-- 
...although Eating Honey was a very good thing to do, there was a
moment just before you began to eat it which was better than when you
were...
                                                      Winnie the Pooh



view thread (68+ messages)  latest in thread

Message-ID: <48F70157.7010601@batory.org.pl>
Permalink:  ../48F70157.7010601@batory.org.pl/
Also on:    postgresql.org/message-id/48F70157.7010601@batory.org.pl

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tometzky@batory.org.pl, mikkel@hoegh.org, pgsql-general@postgresql.org
  Subject: Re: Drupal and PostgreSQL - performance issues?
  In-Reply-To: <48F70157.7010601@batory.org.pl>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox