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
PostgreSQL's worst
[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 serious issues...
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 http://www.php.net/
To
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
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 changed Makefile.in
