On Monday 04 June 2007 17:11:23 Gregory Stark wrote:
> Those plans look like they have a lot of casts to text in them. How have
> you defined your indexes? Are your id columns really text?
project table:
Indexes:
"project_pk" PRIMARY KEY, btree (id)
"project_path" UNIQUE, btree (path)
role table:
Indexes:
"role_pk" PRIMARY KEY, btree (id)
role_default_user table:
Indexes:
"role_def_user_pk" PRIMARY KEY, btree (id)
"role_def_u_prj_idx" UNIQUE, btree (role_id, default_user_class_id,
project_id)
role_operation table:
Indexes:
"role_operation_pk" PRIMARY KEY, btree (id)
"role_oper_obj_oper" btree (object_type_id, operation_category,
operation_name)
"role_oper_role_id" btree (role_id)
sfuser table:
Indexes:
"sfuser_pk" PRIMARY KEY, btree (id)
"sfuser_username" UNIQUE, btree (username)
projectmembership table:
Indexes:
"pjmb_pk" PRIMARY KEY, btree (id)
"pjmb_projmember" UNIQUE, btree (project_id, member_id)
"pjmb_member" btree (member_id)
relationship table:
Indexes:
"relationship_pk" PRIMARY KEY, btree (id)
"relation_origin" btree (origin_id)
"relation_target" btree (target_id)
"relation_type" btree (relationship_type_name)
field_value table:
Indexes:
"field_value_pk" PRIMARY KEY, btree (id)
"f_val_fid_val_idx" UNIQUE, btree (field_id, value)
"field_class_idx" btree (value_class)
"field_value_idx" btree (value)
item table:
Indexes:
"item_pk" PRIMARY KEY, btree (id)
"item_created_by_id" btree (created_by_id)
"item_folder" btree (folder_id)
"item_name" btree (name)
and yes, the 'id' column is always: character varying type
> And you don't have a 7.4 install around to compare the plans do you?
I have a 7.3.19 db, if that would be useful
--
Douglas J Hunley (doug at hunley.homeip.net) - Linux User #174778
http://doug.hunley.homeip.net
Whose cruel idea was it for the word "lisp" to have an "s" in it?
