| From: | Brian Ghidinelli <brian(at)pukkasoft(dot)com> |
|---|---|
| To: | SF Postgres <sfpug(at)postgresql(dot)org> |
| Subject: | Re: Using bitwise operator vs. mapping table |
| Date: | 2007-10-16 02:02:26 |
| Message-ID: | 47141BB2.3030708@pukkasoft.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | sfpug |
David Fetter wrote:
>> However, we're growing and our users run quite a lot of reports
>> which already do 5 or 6-way joins.
>
> Is this actually causing a problem?
EXPLAIN ANALYZE isn't too excited. This is where I think a real DBA
could tweak the queries and indexes a bit to improve the times.
> Premature optimization is the root of all evil.
> Donald E. Knuth,
> ACM Journal Computing Surveys
> Vol 6, No. 4, Dec. 1974. p.268
And optimization permanently left undone is the root of all slow
applications! :) Ok, maybe that's not true either. This application
is 4 years old; it's due for some optimization so I pinged the list to
see if this approach had any advantages.
Brian
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2007-10-16 15:08:06 | Re: Using bitwise operator vs. mapping table |
| Previous Message | elein | 2007-10-15 23:46:49 | [ameli@CS.Berkeley.EDU: DB Seminar: Friday 10/19, 1-2:30pm, 606 Soda Hall] |