On Thu, Sep 08, 2005 at 04:35:51PM +0200, Michael Fuhr wrote:
> On Thu, Sep 08, 2005 at 03:39:50PM +0200, Bohdan Linda wrote:
> commit it now." You have to do some extra bookkeeping and you can't
> commit several prepared transactions atomically (as far as I know),
> but that's one way you could make changes durable without actually
> committing them until later.
In case of durable transactions, would they be released from memory? Thus
could the transaction be more respectfull to the HW when processing too
much data?
And what about nested transactions? Are they planned? The point is
connected to my previous question of the secured access to stored
procedures. If I move part of database logic to the client, I will have to
introduce parameters to the procedures. This may be potentialy abusable.
If I try to use dblink from server to server (both are the same), is there
some perfromance penalty? How big?
Regards,
Bohdan
