On October 28, 2005 2:54 PM
Collin Peters wrote:
I have two tables, one is called 'users' the other is 'user_activity'.
...
I am trying to write a simple query that returns the last time each
user logged into the system. This is how the query looks at the
moment:
SELECT u.user_id,
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Jim C. Nasby
Sent: Friday, September 30, 2005 4:49 PM
Subject: Re: [PERFORM] [HACKERS] Query in SQL statement
I suggest ditching the CamelCase and going with underline_seperators.
I'd also not use the
Jeffrey W. Baker wrote:
On Tue, 2005-08-16 at 10:46 -0700, Roger Hand wrote:
The disks are ext3 with journalling type of ordered, but this was later
changed to writeback with no apparent change in speed.
They're on a Dell poweredge 6650 with LSI raid card, setup as follows:
4 disks raid 10
Ulrich Wisser wrote:
one of our services is click counting for on line advertising. We do
this by importing Apache log files every five minutes. This results in a
lot of insert and delete statements.
...
If you are doing mostly inserting, make sure you are in a transaction,
Well, yes,
Summary
===
We are writing to the db pretty much 24 hours a day.
Recently the amount of data we write has increased, and the query speed,
formerly okay, has taken a dive.
The query is using the indexes as expected, so I don't _think_ I have a query
tuning issue, just an io problem.
The
On March 21, 2005 8:07 AM, Hannu Krosing wrote:
On L, 2005-03-19 at 23:47 -0500, Tom Lane wrote:
Well, partitioning on the primary key would be Good Enough for 95% or
99% of the real problems out there. I'm not excited about adding a
large chunk of complexity to cover another few percent.
