Skip site navigation (1) Skip section navigation (2)

Re: Speeding up this function

From: Matt Nuzum <matt(dot)followers(at)gmail(dot)com>
To: jdunn(at)autorevenue(dot)com
Cc: Postgresql Performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Speeding up this function
Date: 2004-10-19 19:55:04
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
On Tue, 19 Oct 2004 15:49:45 -0400, Jeremy Dunn <jdunn(at)autorevenue(dot)com> wrote:
> > -----Original Message-----
> > From: pgsql-performance-owner(at)postgresql(dot)org
> > [mailto:pgsql-performance-owner(at)postgresql(dot)org] On Behalf Of
> > Matt Nuzum
> > Sent: Tuesday, October 19, 2004 3:35 PM
> > To: pgsql-performance
> > Subject: [PERFORM] Speeding up this function
> >
> <snip>
> This is probably a stupid question, but why are you trying to create
> sessions after the fact?  Since it appears that users of your site must
> login, why not just assign a sessionID to them at login time, and keep
> it in the URL for the duration of the session?  Then it would be easy to
> track where they've been.
> - Jeremy

You don't have to log in to visit the sites.  These log files are
actually for many domains.  Right now, we do logging with a web-bug
and it does handle the sessions, but it relies on javascript and we
want to track a lot more than we are now.  Plus, that code is in
JavaScript and one of our primary motiviations is to ditch MySQL

Matthew Nuzum		| Makers of "Elite Content Management System"		| View samples of Elite CMS in action
matt(at)followers(dot)net		|

In response to

pgsql-performance by date

Next:From: Tom LaneDate: 2004-10-19 21:52:13
Subject: Re: futex results with dbt-3
Previous:From: Jeremy DunnDate: 2004-10-19 19:49:45
Subject: Re: Speeding up this function

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group