Robert wrote:
>
> ...
>
> Indeed, that's exactly what Apache::Session::Store::Postgres does... so,
> Gerald, there's no need for Semaphore after all, is it?
>
> However, Angus complaints 11/5/01 that under Embperl, DESTROY is never
> called and so no session is ever commited, but this is separate problem.
So, with this config and Angus' patch %udat works OK
PerlSetEnv EMBPERL_SESSION_CLASSES "Postgres Null Base64"
PerlSetEnv EMBPERL_SESSION_ARGS "DataSource=dbi:Pg:dbname=sessions
UserName=postgres Commit=1"
I still have few idle postgres backends - their number doesn't seem to
grow fast, maybe it corresponds to the number of new sessions... It
looks like the lock is not released after insert'ing new session but
afterwards everything works. Does this make sense?
- Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
