Skip site navigation (1) Skip section navigation (2)

Re: [GENERAL] Postgres vs commercial products

From: Wilson MacGyver <macgyver(at)ruri(dot)cylatech(dot)com>
To: joden(at)lee(dot)k12(dot)nc(dot)us (James Olin Oden)
Cc: scrappy(at)hub(dot)org, herouth(at)oumail(dot)openu(dot)ac(dot)il, cmj(at)inline-design(dot)com, pgsql-general(at)postgreSQL(dot)org
Subject: Re: [GENERAL] Postgres vs commercial products
Date: 1998-07-28 19:41:01
Message-ID: 199807281941.PAA07839@ruri.cylatech.com (view raw or flat)
Thread:
Lists: pgsql-general
>   That is the real problem.  I have to assume whenever you start implementing raw
> devices, you go far far away from DBMS design to OS design.  Perhaps you do not
> have to write the process control part of an OS, but (I mean this jokingly) in
> one's arrogance one must think you can access the HD's more efficiently than the
> OS can.  Hey, maybe some can do this, and have enough knowledge about HD's and
> controllers to do this, but making this portable is got to a _lot_ of work.
> 
> Not that it couldn't be done, or that it wouldn't be eventually a good idea
> (*though I am not certain about that)...james

this reminds me so much of the multi threading issue Sybase faced. When they
were adding support for multi threading, every Unix has different level of
support that they end up added their own threading engine.

I for one, don't see RAW device support in Postgres has a "critial" missing
feature, in my thinking, there are other things that are more important.
Though for something like RDBMS, where each person's need could be 
so different, it truly is YMMV.




In response to

pgsql-general by date

Next:From: Andrew GibsonDate: 1998-07-28 23:57:05
Subject: Mac Connectivity
Previous:From: BoersenspielteamDate: 1998-07-28 17:34:50
Subject: Re: [GENERAL] Postgres vs commercial products

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group