Aug 25 14:53:33 forgehouse-s1 postgres[23723]: [2-1] LOG: duration:
1192.789 ms statement: UPDATE session SET hit_time=now() WHERE
md5='d84613009a95296fb511c2cb051ad618';
Aug 25 14:53:53 forgehouse-s1 postgres[23727]: [2-1] LOG: duration:
12159.162 ms statement: UPDATE session SET
On Fri, Aug 26, 2005 at 02:27:04PM +0100, Aldor wrote:
Aug 25 14:53:33 forgehouse-s1 postgres[23723]: [2-1] LOG: duration:
1192.789 ms statement: UPDATE session SET hit_time=now() WHERE
md5='d84613009a95296fb511c2cb051ad618';
Aug 25 14:53:53 forgehouse-s1 postgres[23727]: [2-1] LOG:
'k, I've been wracking my brains over this today, and I'm either
mis-understanding what is being reported *or* its reporting wrong ...
According to syslog:
LOG: duration: 4107.987 ms statement: UPDATE session SET hit_time=now() WHERE
md5='8b8e7b7ff9b1b2ed5fc60218ced28d00';
But, if I do
As I know EXPLAIN ANALYZE runs the query. I think you are just running
the query two times. The first time you run the query it will take a
long time to be processed - after the first run the query planner will
remember the best way to run the query so your second run runs much faster.
I can
On Thu, 25 Aug 2005, Aldor wrote:
As I know EXPLAIN ANALYZE runs the query. I think you are just running the
query two times. The first time you run the query it will take a long time to
be processed - after the first run the query planner will remember the best
way to run the query so your
On Thu, Aug 25, 2005 at 03:56:36PM -0300, Marc G. Fournier wrote:
On Thu, 25 Aug 2005, Aldor wrote:
I'm still wondering why you first query takes about 4107.987 ms - this
kind of query has usually have to run much much faster.
That would work if I were to get really occasional high values
On Thu, Aug 25, 2005 at 01:55:08PM -0600, Michael Fuhr wrote:
Are the updates happening inside a transaction? Is it possible
that they're being blocked by other transactions that update the
same record around the same time and don't commit immediately?
I can duplicate the results you're
Aug 25 14:53:32 forgehouse-s1 postgres[23721]: [2-1] LOG: duration:
567.559 ms statement: UPDATE session SET hit_time=now() WHERE
md5='7537b74eab488de54d6e0167d1919207';
Aug 25 14:53:32 forgehouse-s1 postgres[23722]: [2-1] LOG: duration:
565.966 ms statement: UPDATE session SET
On Fri, Aug 26, 2005 at 12:50:29AM +0100, Aldor wrote:
Aug 25 14:53:32 forgehouse-s1 postgres[23721]: [2-1] LOG: duration:
567.559 ms statement: UPDATE session SET hit_time=now() WHERE
md5='7537b74eab488de54d6e0167d1919207';
Aug 25 14:53:32 forgehouse-s1 postgres[23722]: [2-1] LOG:
On Thu, 25 Aug 2005, Michael Fuhr wrote:
On Fri, Aug 26, 2005 at 12:50:29AM +0100, Aldor wrote:
Aug 25 14:53:32 forgehouse-s1 postgres[23721]: [2-1] LOG: duration:
567.559 ms statement: UPDATE session SET hit_time=now() WHERE
md5='7537b74eab488de54d6e0167d1919207';
Aug 25 14:53:32
10 matches
Mail list logo
