[COLUG] Market review

[Balint, Jess]

With PostgreSQL, you cannot allocate certain files to a database. A
commercial database will allow you to allocate chucks (raw disk or cooked
files) to a database so that you can make good use of more disks, ie split
purchase data by months on different disks.

The performance increases on raw disks are obtained because a) there is no
filesystem overhead and b) there database is transferred directly to memory
without kernel interaction.

What file management utilities does the software vendor even distribute?

> -----Original Message-----
> From: Jim Wildman [mailto:jim at rossberry.com]
> Sent: Thursday, July 03, 2003 4:50 PM
> To: colug at colug.net
> Subject: Re: [COLUG] Market review
> 
> 
> The advantage goes to the sw vendor because you have to use their file
> management utilities.  If you really need more speed, go to a wider
> array (ie stripe across more spindles).
> 
> --------------------------------------------------------------
> ----------
> Jim Wildman, CISSP, RHCE                                
> jim at rossberry.com
> http://www.rossberry.com
> 
> On Thu, 3 Jul 2003, Pat Collins wrote:
> 
> > On Thu, Jul 03, 2003 at 10:36:50AM -0400, Balint, Jess wrote:
> > > for databases. In PostgreSQL, you must use a file in the 
> filesystem. And
> > > querying across databases? Even server instances? Unthinkable....
> > > 
> > 
> > Besides speed (maybe a slight advantage on raw disk) what 
> is the difference 
> > between raw disk and mounting on a file system.  Is it data 
> integratity, 
> > tool support, what exactly makes raw disk support better?
> > 
> > Pat
> > _______________________________________________
> > colug mailing list
> > colug at colug.net
> > http://www.colug.net/mailman/listinfo/colug
> > 
> 
> _______________________________________________
> colug mailing list
> colug at colug.net
> http://www.colug.net/mailman/listinfo/colug
>