An index
on cp and effectif would help your first query. An index on naf, cp and effectif would help your second
query.
Something
like this:
CREATE INDEX base_aveugle_cp_key2 ON
base_aveugle USING btree (cp, effectif);
CREATE INDEX base_aveugle_naf_key2 ON base_aveugle USING btree
Title: RE: [PERFORM] postgres 7.4 at 100%
Creating indexes on a table affects insert performance depending on the number of indexes that have to be populated. From a query standpoint, indexes are a godsend in most cases.
Duane
-Original Message-
From: Chris Cheston [mailto:[EMAIL P
Title: RE: [PERFORM] is it possible to for the planner to optimize this form?
I didn't really look that closely at the problem but have you thought of trying:
select t.key, t.field from t a
, (select count(*) as cntb from t b
where b.field > a.field) as dmytbl
where
cntb = k
T
Title: RE: [PERFORM] Trigger & Function
Thanks for the response. I was pretty sure it couldn't be done the way I wanted to but felt I would ask anyway.
Thanks again,
Duane
-Original Message-
From: Mike Nolan [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 01, 2004 3:04 PM
To: [EMAI
Title: Trigger & Function
I'm trying to create a trigger (AFTER INSERT, UPDATE, DELETE) as an audit routine inserting into an audit table the "before" and "after" views of the row being acted upon. My problem is I defined the "before" and "after" fields in the audit table as TEXT and when I t
Title: Hardware Platform
I'm working on a project using PostgreSQL as our database designing a budget system. We are still in the design and testing phases but I thought I would ask advice about a platform to host this system.
We aren't a large system, probably no more than 50-75 users at an
