Note that the innefficiency could well lie with Informix's file system interfacing as easily as it could lie with the operating system. Do they charge extra for being able to access raw devices or somehow make more money by supporting them? If so, there could be a clear business case for lots of uwaits() in the code path that handles file systems.
I'm just saying it's a possibility. On Tue, 6 Apr 2004, Gregory S. Williamson wrote: > Remarkable, perhaps, to you. Not in the Informix world. But irrelevant to postgres, > no ? > > -----Original Message----- > From: Chris Browne [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 06, 2004 1:57 PM > To: [EMAIL PROTECTED] > Subject: Re: [ADMIN] Raw devices vs. Filesystems > > > [EMAIL PROTECTED] ("Gregory S. Williamson") writes: > > No point to beating a dead horse (other than the sheer joy of the > > thing) since postgres does not have raw device support, but ... raw > > devices, at least on solaris, are about 10 times as fast as cooked > > file systems for Informix. This might still be a gain for postgres' > > performance, but the portability issues remain. > > That claim seems really rather remarkable. > > It implies an entirely stunning degree of inefficiency in the > implementation of filesystems on Solaris. > > The amount of indirection involved in walking through i-nodes and such > is something I would expect to introduce some percentage of > performance loss, but for it to introduce overhead of over 900% > presumably implies that Sun (and/or Veritas) got something really > horribly wrong. > ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
