On Monday, September 15, 2003, at 02:06 PM, Gaetano Mendola wrote:
""Matt Clark"" <[EMAIL PROTECTED]> wrote:It'd be easy to automate all except the explain, a script that dideverything else could then emit "If your preoblem relates to aspecific query, then run 'explain analyze <query>' and attach it to yourmessage 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
sounds good. maybe with the option (enabled by default?) to only show the columns used in the queries for the tables pulled. ((wheat from chaff and all that))
hmm. though there's still the (some small percentage of) things that could be going wrong with custom stored procedures. dumping those would be (I'm presuming, based on the scope of the task as it's been described) reasonably simply, but figuring out what they touch could be prohibitive?
kudos for any attempt, though, all around. :)
-kaolin fire -postgresql novice -http://poemranker.com
---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
