Gurpreet Sachdeva wrote:
I have recently transfered a big database on my master node of a 4
node openSSI Cluster... The system is working fine but sometimes, I
get following errors:
http://192.168.1.100/cgi-bin/search.py File
/usr/lib/python2.2/site-packages/pyPgSQL/PgSQL.py, line 3067, in
On Fri, Dec 17, 2004 at 11:51:12PM -0800, Ron Mayer wrote:
Any advice for settings for extremely IO constrained systems?
A demo I've set up for sales seems to be spending much of it's time in
disk wait states.
The particular system I'm working with is:
Ext3 on Debian inside
On Fri, 2004-12-17 at 23:51 -0800, Ron Mayer wrote:
Any advice for settings for extremely IO constrained systems?
A demo I've set up for sales seems to be spending much of it's time in
disk wait states.
The particular system I'm working with is:
Ext3 on Debian inside Microsoft
A demo I've set up for sales seems to be spending much of it's time in
disk wait states.
The particular system I'm working with is:
Ext3 on Debian inside Microsoft VirtualPC on NTFS
on WindowsXP on laptops of our sales team.
As this is only for demo purposes, you might
Sorry for the late reply, so I included the whole thread. Should this be
a TODO?
On Wed, Dec 15, 2004 at 08:30:08PM -0500, Tom Lane wrote:
Greg Stark [EMAIL PROTECTED] writes:
But I'm a bit puzzled. Why would Append have any significant cost? It's just
taking the tuples from one plan node
On Wed, Dec 15, 2004 at 11:56:40AM -0800, Josh Berkus wrote:
Greg,
Well Oracle has lots of partitioning intelligence pushed up to the planner
to avoid overhead.
If you have a query with something like WHERE date = '2004-01-01' and
date is your partition key (even if it's a range) then
