Re: PostgreSQL runs a query much slower than BDE and MySQL

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Peter Hardman" <peter(at)ssbg(dot)zetnet(dot)co(dot)uk>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: PostgreSQL runs a query much slower than BDE and MySQL
Date: 2006-08-18 00:31:51
Message-ID: 965.1155861111@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

"Peter Hardman" <peter(at)ssbg(dot)zetnet(dot)co(dot)uk> writes:
> On 17 Aug 2006 at 14:33, Tom Lane wrote:
>> I found a couple of minor planner problems, which I've repaired in CVS
>> HEAD. You might consider using TEXT columns instead of VARCHAR(n),

> As someone else suggested, these fields ought really to be CHAR no VARCHAR.

That should be fine too. VARCHAR is sort of a poor stepchild in
Postgres, because it piggybacks on TEXT's operators --- but CHAR
has different comparison rules, hence its own operators, hence
doesn't trip over that bug.

There's still some things that don't add up to me, like the question
of the pkey column order. Will look some more.

regards, tom lane

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message mark 2006-08-18 00:33:27 Q: Performance of join vs embedded query for simple queries?
Previous Message Scott Lamb 2006-08-17 22:00:52 Re: PostgreSQL runs a query much slower than BDE and MySQL