Re: pgbench create index anomoly - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: pgbench create index anomoly
Date
Msg-id 1148327660.2755.106.camel@localhost.localdomain
Whole thread Raw
In response to pgbench create index anomoly  ("Jim C. Nasby" <jnasby@pervasive.com>)
Responses Re: pgbench create index anomoly  ("Jim C. Nasby" <jnasby@pervasive.com>)
List 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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Update on sort-compression stuff
Next
From: "Jim C. Nasby"
Date:
Subject: Re: pgbench create index anomoly