Hi, there,
I am running PostgreSQL 7.3.4 on MAC OS X G5 with dual processors and
8GB memory. The shared buffer was set as 512MB.
The database has been running great until about 10 days ago when our
developers decided to add some indexes to some tables to speed up
certain uploading ops.
Now the CPU
Our product (Sophos PureMessage) runs on a Postgres database.
Some of our Solaris customers have Oracle licenses, and they've
commented on the performance difference between Oracle and Postgresql
on such boxes. In-house, we've noticed the 2:1 (sometimes 5:1)
performance difference in inserting row
Mischa Sandberg <[EMAIL PROTECTED]> writes:
> Our product (Sophos PureMessage) runs on a Postgres database.
> Some of our Solaris customers have Oracle licenses, and they've
> commented on the performance difference between Oracle and Postgresql
> on such boxes. In-house, we've noticed the 2:1 (so
Hi,
I'm using PostgreSQL 7.4 on a table with ~700.000 rows looking like this:
Table "public.enkeltsalg"
Column | Type | Modifiers
+--+-
Mischa Sandberg wrote:
In the meantime, what I gather from browsing mail archives is that
postgresql on Solaris seems to get hung up on IO rather than CPU.
Well, people more knowledgeable in the secrets of postgres seem
confident that this is not your problem. Fortunetly, however, there is a
sim
"Steinar H. Gunderson" <[EMAIL PROTECTED]> writes:
> Now, my first notion was creating a functional index to help the planner:
> ...
> However, this obviously didn't help the planner (this came as a surprise to
> me, but probably won't come as a surprise to the more seasoned users here :-)
7.4 doe
On Sat, Sep 18, 2004 at 03:48:13PM -0400, Tom Lane wrote:
> 7.4 doesn't have any statistics on expression indexes. 8.0 will do what
> you want though. (I just fixed an oversight that prevented it from
> doing so...)
OK, so I'll have to wait for 8.0.0beta3 or 8.0.0 (I tried 8.0.0beta2, it gave
me
I have currently implemented a schema for my "Dating Site" that is storing
user search preferences and user attributes in an int[] array using the
contrib/intarray package (suggested by Greg Stark). But there are a few
problems.
a) query_int can't be cast to int4.
b) query_int ca
Patrick Clery <[EMAIL PROTECTED]> writes:
> PLAN
> -
> Limit
