Re: Postgres performance issue - Mailing list pgsql-general

From Len Morgan
Subject Re: Postgres performance issue
Date
Msg-id 003801c0e787$9db59c20$0908a8c0@H233.bstx.cc
Whole thread Raw
In response to Postgres performance issue  (Linh Luong <lluong@home.com>)
List pgsql-general
>select * from customer where upper(name) like  upper('$criteria%')
>
>Does anyone know what the limitation on Postgres? Like how many records
>before it starts to seize and choke on the performance side?

I don't think it's choking on the server side.  How many records would you
expect to get back if you select ALL records?  If there are a lot of them,
you may be running out of memory on your client (PHP in this case) or it's
allocating space for each record as it comes in which may be what's causing
your performance hit.  Also, if you can determine that ALL records are being
requested, it would be faster to remove the LIKE clause since this requires
the server to examine each record whereas just a SELECT * from customer
doesn't.

len morgan


pgsql-general by date:

Previous
From: mordicus
Date:
Subject: Re: Functional Indices
Next
From: "holtzman"
Date:
Subject: restore pg_dumpall problem with update 7.0.3 to 7.1.1