Re: Transaction Speed and real time database

[please use "reply to all", otherwise you'll have what you just had: the
guy who you write goes home for the weekend and all the rest of the
people on the list who would answer you won't know there is soemthing to
answer...]

On Fri, 2006-07-21 at 13:39, moises wrote:
> Sorry if I can't explain me clear.
> I want to use an extension of postgres, (because I'm very clear that
> postgres is not a real time database.)
> I want to modify some modules of postgres for this convenience, for example,
> add some time constrains to transactions, I know that is a very hard work,
> Our Applications are 100% real time works, controlling industrial process,
> and not OLAP or OLTP applications.
>
> My question is how many fast are postgres in transaction actually? Because
> maybe we don't need to work, in looking for more speed, just constrains and
> planners.

I have to admit RT is for me just a vague idea I still remember from
some courses, but I'm not sure if RT and transactional is compatible at
all... do you really need a transactional data base for RT applications
? Cause postgres is just that, an excellent transactional DB, which BTW
is fast enough for transactional work (where you expect that sometimes
operations fail due to others working in parallel). I'm not sure in
industrial RT applications you could afford failures due to
concurrency... and in that case you would be better off using something
non-transactional - but this is just my limited understanding of the
problem. Others on this list might know better...

Cheers,
Csaba.