Re: pgbench create index anomoly

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pgbench create index anomoly
Date: 2006-05-22 19:54:20
Message-ID: 1148327660.2755.106.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 2006-05-22 at 14:01 -0500, Jim C. Nasby wrote:
> While setting up for the compressed sort testing...
>
> NOTICE: ALTER TABLE / ADD PRIMARY KEY will create implicit index "accounts_pkey" for table "accounts"
> LOG: begin index sort: unique = t, workMem = 16384, randomAccess = f
> LOG: begin index sort: unique = t, workMem = 16384, randomAccess = f

If you set log_line prefix to something that allows us to differentiate
those lines we might be able to identify them. The second line could
well be from a heap sort executed on a different backend; 1024 is the
default work_mem. Some psql commands use hidden SQL with an ORDER BY, so
you can sometimes be a little confused from the log.

Happy to look into it if there really is something wierd going on.

--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim C. Nasby 2006-05-22 20:01:31 Re: pgbench create index anomoly
Previous Message Tom Lane 2006-05-22 19:42:28 Re: Update on sort-compression stuff