From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
---|---|
To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_advisor schema proof of concept |
Date: | 2004-03-25 21:59:33 |
Message-ID: | 1080251973.11890.485.camel@camel |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 2004-03-25 at 11:31, Fabien COELHO wrote:
>
> > > Also, if they have a partial index on the FK, it's not good enough! In
> > > CVS, IS NOT NULL partial indexes should be used, but in general all
> > > others still won't...
> >
> > Whoa, there, partner! Keep in mind that there are *often* reasons for using
> > a partial index on an FK, or even no index at all! The docs for pg_advisor
> > need to reflect that it only catches little details the developer might
> > otherwise have missed. It's not smarter than a DBA.
>
> Sure.
>
> That's why advices are "graded" from info to error in the current
> preliminary version.
>
> Advices that may or may not be good depending on undecidable elements
> have a lower grade. For instance, most attributes should be "NOT NULL"
> from a statistical point of view, but it is perfectly legitimate to
> have nullable attributes mostly anywhere, so the corresponding advices
> is just an "info".
>
Are you planning on making some type of differentiation on advise that
is performance based rather than advise that is theory based? I see
both cases being hinted at and it seems like a subtle but important
piece of information...
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2004-03-25 22:02:40 | Re: HEAD compile troubles |
Previous Message | Bruce Momjian | 2004-03-25 21:55:50 | Re: Log rotation |