[PHP-DEV] session_pgsql module commit notice

Hi all, This is the last notice before PostgreSQL session save handler module commit. I've renamed it to session_pgsql so that users will understand it's a sub module for session module. I've also changed Makefile.in so that php_session.h is installed. Other headers will be installed. If you ca

Re: [PHP-DEV] session_pgsql module commit notice

mlwmohawk wrote: > On Friday 21 December 2001 04:36 am, Yasuo Ohgaki wrote: > >>Hi all, >> >>This is the last notice before PostgreSQL session save handler >>module commit. >> >>I've renamed it to session_pgsql so that users will understand >>it's a sub module for session module. >> >>I've also

Re: [PHP-DEV] session_pgsql module commit notice

I thought some people interested in my ToDo list for pgsql session save handler. - Optional SERIALIZABLE transaction isolation level. - Automatic Failover (connect to other DB. I sync data. so old session info will lost, but web app runs at least :) - Automatic load balance (distrib

Re: [PHP-DEV] session_pgsql module commit notice

mlwmohawk wrote: > On Friday 21 December 2001 10:45 pm, Yasuo Ohgaki wrote: > I was thinking about a PostgreSQL session manager. How is that going to >>>work? IMHO PostgreSQL (currently) is completely wrong for such a task. >>> >>I'm well aware of the issue you mentioned :) >> >> >>>Pos

Re: [PHP-DEV] session_pgsql module commit notice

On Sat, 22 Dec 2001, Yasuo Ohgaki wrote: > Anyone care to take benchmarks? > (You need to wait a little more, since session module needed > to be changed to work with pgsql session save handler) What should be fixed there? Derick -- PHP Development Mailing List To unsub

Re: [PHP-DEV] session_pgsql module commit notice

[EMAIL PROTECTED] wrote: > On Sat, 22 Dec 2001, Yasuo Ohgaki wrote: > > >>Anyone care to take benchmarks? >>(You need to wait a little more, since session module needed >>to be changed to work with pgsql session save handler) >> > > What should be fixed there? > > Derick > > There are seri

[PHP-DEV] pgsql session save handler bench (was [PHP-DEV] session_pgsql module commit notice)

PostgreSQL has one real behavior problem. Updates act as if you do a delete then an insert, i.e. for transactional isolation, an updated row is added new, and the old one is marked as deleted. Sessions are all about updates, and any really active server cluster will expose