Skip site navigation (1) Skip section navigation (2)

Re: pg_advisor schema proof of concept

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>,PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_advisor schema proof of concept
Date: 2004-03-26 07:14:15
Message-ID: Pine.GSO.4.58.0403260807400.4712@elvis (view raw or flat)
Thread:
Lists: pgsql-hackers
Dear Josh,

> > 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...

The current working status is that advices have a grade (info notice
warning error) and a kind (design, performance, meta).

More precise and subtle classification can be though of, but the interest
depends on the total number of advices in the system. Now there is around
a dozen of them, so there is no urge. It is easy to add some more
classification if needed.

Another place where such information can be given is within the
description which illustrate the advice. I think maybe this would be a
better place.

> LAMP = Linux Apache {middleware} Postgres

[JOKE] What about renaming postgreSQL myPostgres? ;-)

-- 
Fabien Coelho - coelho(at)cri(dot)ensmp(dot)fr

In response to

pgsql-hackers by date

Next:From: Richard HuxtonDate: 2004-03-26 07:15:22
Subject: Re: pg_advisor schema proof of concept
Previous:From: Manfred SpraulDate: 2004-03-26 06:25:53
Subject: Re: [HACKERS] fsync method checking

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group