Diehl,
> Um no, I just need a smaller problem to solve. The database worked
> quite
> well when the problem was half this size.
<snip>
> could do with 60 day's...!" And they are right, if it can be done...
> If it
> can't, I'll tell them and they will understand.
What I'm saying is, based on your description, you need a lot of hand-on
performance tuning help. Someone who knows the pgsql performance
parameters and can experiment with tweaking and tuning to avoid swamping
the memory of the machine(s) you're running on. Because that's what it
sounds like the problem is.
However, that sort of help will take some paid consultant time and
possibly hardware. I think that if you can run a query on 150gb of
data, you can probably run it on 355gb ... you just need some help
performance tuning. But I don't think general advice on a list is gonna
do it, y'know?
-Josh
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology [EMAIL PROTECTED]
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
