Re: Report Generator Proposal

""Matt Clark"" <matt(at)ymogen(dot)net> wrote:
> It'd be easy to automate all except the explain, a script that did
everything else could then emit "If your preoblem relates to a
> specific query, then run 'explain analyze <query>' and attach it to your
message as well".

Well, must be charge of psql store somewhere all selects performed
between the BEGIN REPORT and END REPORT and perform
the explain command of that selects with the explain; may be the really
difficult here is that psql
shall know all tables involved in a select and insert in the report the
descriptions of that tables.
Before to work on it I want be sure that is a good idea.

Regards
Gaetano Mendola

> > -----Original Message-----
> > From: pgsql-admin-owner(at)postgresql(dot)org
> > [mailto:pgsql-admin-owner(at)postgresql(dot)org]On Behalf Of Gaetano Mendola
> > Sent: 15 September 2003 16:25
> > To: pgsql-admin(at)postgresql(dot)org
> > Subject: Re: [ADMIN] Report Generator Proposal
> >
> >
> > Must I suppose that the idea rejected ?
> >
> > ----- Original Message -----
> > From: ""Gaetano Mendola"" <mendola(at)bigfoot(dot)com>
> > Newsgroups: comp.databases.postgresql.admin
> > Sent: Thursday, September 11, 2003 11:52 PM
> > Subject: Re: Report Generator Proposal
> >
> >
> > > Nobody entusiastic ? I'm wrong about my feeling ?
> > > I think that have the psql able to generate a report
> > > will increase the our better response to a user novice
> > > or not ?
> > >
> > >
> > > Regards
> > > Gaetano Mendola
> > >
> > > ----- Original Message -----
> > > From: ""Gaetano Mendola"" <mendola(at)bigfoot(dot)com>
> > > Newsgroups: comp.databases.postgresql.admin
> > > Sent: Wednesday, September 10, 2003 4:10 AM
> > > Subject: Report Generator Proposal
> > >
> > >
> > > > Hi all,
> > > > each time that someone say: this query is slow, this query take
forever,
> > > bla
> > > > bla bla
> > > > all our request are:
> > > >
> > > > 1) Which version are you running ?
> > > > 2) May I see your table definition?
> > > > 3) May I see you configuration file?
> > > > 4) May I see the explain ?
> > > > 5) .......
> > > >
> > > > sometimes a beginner is scared about all these questions and even
> > > > he/she don't know how do collect these informations and we lose
> > > > important data about: "why that damn query is too slow"?
> > > >
> > > >
> > > > may be is usefull generate an automatic report that take charge
> > > > of collect all these informations and send it to a file or directly
to
> > > > pgsql-performance(at)postgresql(dot)org , may be something like:
> > > >
> > > >
> > > > > BEGIN REPORT TO FILE <file_name>
> > > > > SELECT ......
> > > > > END REPORT;
> > > >
> > > >
> > > > or
> > > >
> > > >
> > > > > BEGIN REPORT TO EMAIL <address>
> > > > > SELECT ......
> > > > > END REPORT;
> > > >
> > > >
> > > >
> > > > Regards
> > > > Gaetano Mendola
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > ---------------------------(end of
broadcast)---------------------------
> > > > TIP 8: explain analyze is your friend
> > > >
> > >
> > >
> > > ---------------------------(end of
broadcast)---------------------------
> > > TIP 1: subscribe and unsubscribe commands go to
majordomo(at)postgresql(dot)org
> > >
> >
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 8: explain analyze is your friend
> >
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
>