On Fri, Nov 20, 2009 at 7:27 PM, Greg Smith wrote:
> Richard Neill wrote:
>>
>> The key issue for short,fast transactions seems to be
>> how fast an fdatasync() call can run, forcing the commit to disk, and
>> allowing the transaction to return to userspace.
>> Attached is a short C program which
Hi,
My PostgreSQL server has two CPUs (OS: Fedora 11), each with 4 cores. Total
is 8cores. Now I have several clients running at the same time to do insert
and update on the same table, each client having its own connection. I have
made two testing with clients running in parallel to load 20M
afancy writes:
> My PostgreSQL server has two CPUs (OS: Fedora 11), each with 4 cores. Total
> is 8cores. Now I have several clients running at the same time to do insert
> and update on the same table, each client having its own connection. I have
> made two testing with clients running in pa
Hi all,
The query below is fairly fast if the commented sub-select is
commented, but once I included that column, it takes over 10 minutes to
return results. Can someone shed some light on it? I was able to redo
the query using left joins instead, and it only marginally increased
result time. T
Hi all,
(Sorry, I know this is a repeat, but if you're using message threads,
the previous one was a reply to an OLD subject.)
The query below is fairly fast if the commented sub-select is
commented, but once I included that column, it takes over 10 minutes to
return results. Can someone shed s
