<div dir="ltr"><div class="gmail_quote">2009/12/16 decibel <span dir="ltr"><<a
href="mailto:decibel@decibel.org">decibel@decibel.org</a>></span><br/><blockquote class="gmail_quote"
style="border-left:1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On Dec
11,2009, at 8:44 PM, Tom Lane wrote:<br /> > Bruce Momjian <<a
href="mailto:bruce@momjian.us">bruce@momjian.us</a>>writes:<br /> >> Ashish wrote:<br /> >>> I am
thinkingabout starting with the following TODO item:<br /> >>> --> Have EXPLAIN ANALYZE issue NOTICE
messageswhen the estimated<br /> >>> and actual row counts differ by a specified percentage.<br /> ><br />
>>I even have a sample patch you can use as a start, attached.<br /> ><br /></div><div class="im">> IMO the
hardpart of the TODO item is to design a useful user interface<br /> > for highlighting specific EXPLAIN entries
(andNOTICE messages probably<br /> > ain't it either). Getting the numbers is trivial.<br /><br /></div>What about
prefixingexplain output with line numbers? NOTICEs (or whatever mechanism) could then reference the line numbers.<br
/><br/></blockquote></div><br />+1<br clear="all" /><br />-- <br />Lets call it Postgres<br /><br />EnterpriseDB
<ahref="http://www.enterprisedb.com">http://www.enterprisedb.com</a><br /><br />gurjeet[.singh]@EnterpriseDB.com<br
/><br/> singh.gurjeet@{ gmail | hotmail | indiatimes | yahoo }.com<br />Twitter: singh_gurjeet<br />Skype:
singh_gurjeet<br/><br />Mail sent from my BlackLaptop device<br /></div>
