Re: Ada and PL/pgSQL ?

["björn lundin" <b.f.lundin@gmail.com>]

Den fredagen den 9:e maj 2014 kl. 18:26:22 UTC+2 skrev sdale...@gmail.com:

>With a majority of the slow down occuring from table locks on db transactions.

Thinking a bit of this.
If you have the same figures with Postgres, as you state,
then I wonder if your code is explicitly locking the tables?

As in issuing a statement like 'LOCK TABLE XYZ' or
'SELECT XYZ for UPDATE'

That is killing performance in any db.

If so, and you migrate that principle, you will always have performance issues.
If so, you'll need to use other mechanisms to ensure your data is untampered with, as in having versions/timestamps on each row, and check that the row-version you first read, is the same at write (essentially using a where-clause having 'where version=originally_read_version' in it. 

And if rows affected is 0, rollback and start-over, given you wanted to update 1 row). Scoop of transactions becomes very important here

Basically, what my posts are trying to say is that
the timings you describe will likely not get better by putting your logic in the database. Putting you logic in Ada, will however likely make your maintenance burden a lot easier

/Björn