In our last installment, we saw that JFS provides higher pgbench
performance than either XFS or ext3. Using a direct-I/O patch stolen
from 8.1, JFS achieved 105 tps with 100 clients.
To refresh, the machine in question has 5 7200RPM SATA disks, an Areca
RAID controller with 128MB cache, and 1GB
On Sat, Jul 16, 2005 at 01:12:27AM -0700, Jeffrey W. Baker wrote:
Another frequent suggestion is to put the xlog on a separate device. I
tried this, and, for a given number of disks, it appears to be
counter-productive. A RAID5 of 5 disks holding both logs and data is
about 15% faster than a
At Fri, 15 Jul 2005 14:39:36 -0600,
Ron Wills wrote:
I just wanted to thank everyone for their help. I believe we found a
solution that will help with this problem, with the hardware
configuration and caching the larger tables into smaller data sets.
A valuable lesson learned from this ;)
Postgres Version:
7.3.9 and 8.0.1 (different sites use different versions depending on when
they first installed Postgres)
Migration Plans:
All sites on 8.n within the next 6-9 months.
Scenario:
A temporary table is created via a SELECT blah INTO TEMPORARY TABLE blah
FROM The SELECT
Steven Rosenstein [EMAIL PROTECTED] writes:
Are there any performance issues or considerations associated with using a
temporary table in this scenario?
It's probably worthwhile to ANALYZE the temp table after it's filled,
before you start joining to it.
regards, tom
