Alex,
you explained that global-sync cache mode only works within a txn.
I thought that per-transaction cache mode does this, and that global
sync extends this behaviour so transactions/threads can share the
cache?
If not, what's the difference between them?
Leslie
__
??>> this cache mode (and postmodern backend in general) is oriented on
??>> webserver-like workload -- each web request always is wrapped into
??>> transaction. if request does no DB activity, that's OK -- starting txn
??>> overhead is not that significant on scale of typical HTTP request
??>> ti
> this cache mode (and postmodern backend in general) is oriented on
> webserver-like workload -- each web request always is wrapped into
> transaction. if request does no DB activity, that's OK -- starting txn
> overhead is not that significant on scale of typical HTTP request time. but
> many re
??>> but if you do not start your transactions explicitly, enclosing as
??>> many operations as posible, global-sync-cache absolutely makes no
??>> sense -- it takes more effort to synchornize changes than to actually
??>> load value from database, if that's just a single value. so, maybe, if
??>>
Dear Alex,
> it seems you didn't wrap your code into explicit transaction.
Thanks for your quick analysis.
> but if you do not start your transactions explicitly, enclosing as many
> operations as posible, global-sync-cache absolutely makes no sense -- it
> takes more effort to synchornize cha
??>> can you catch a backtrace? it seems to be quite relevant here
LPP> 6: (LAMBDA NIL)
LPP> At
LPP> /home/sky/projects/mystic/hg.beta1/packages/elephant/src/db-postmodern
LPP> /pm-sql.lisp:1577: (LAMBDA NIL)
LPP> At
LPP> /home/sky/projects/mystic/hg.beta1/packages/elephant/src/db-postmo
> LPP> With this enabled I sometimes get
>
> LPP> Database error 55000: currval of sequence "txn_id" is not yet LPP>
> defined
in this session
>
> can you catch a backtrace? it seems to be quite relevant here
6: (LAMBDA NIL)
At
/home/sky/projects/mystic/hg.beta1/packages/elephant/src/d
