Re: Query performance issue

From: Venkat Balaji <venkat(dot)balaji(at)verse(dot)in>
To: Jayadevan M <Jayadevan(dot)Maymala(at)ibsplc(dot)com>
Cc: PGSQL Performance <pgsql-performance(at)postgresql(dot)org>, pgsql-performance-owner(at)postgresql(dot)org, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Subject: Re: Query performance issue
Date: 2011-08-31 11:32:58
Message-ID: CAFrxt0jTkVq1RjuRr=SHn9sXBJm7kG0B8LZ7fmt_UzX6ZxDF2w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Missed out looping in community...

On Wed, Aug 31, 2011 at 5:01 PM, Venkat Balaji <venkat(dot)balaji(at)verse(dot)in>wrote:

> Could you help us know the tables and columns on which Indexes are built ?
>
> Query is performing sorting based on key upper(column) and that is where i
> believe the cost is high.
>
> The 'upper' function is used up in the where clause?
>
> Thanks
> Venkat
>
>
> On Wed, Aug 31, 2011 at 4:49 PM, Jayadevan M <Jayadevan(dot)Maymala(at)ibsplc(dot)com
> > wrote:
>
>> Hello,
>>
>> > >
>> > > Please run EXPLAIN ANALYZE on the query and post that, it's hard to
>> say
>> > > what's wrong from just the query plan, without knowing where the time
>> is
>> > > actually spent.
>> > Here is the explain analyze
>> > http://explain.depesz.com/s/MY1
>>
>> Going through the url tells me that statistics may be off. I will try
>> analyzing the tables. That should help?
>> Regards,
>> Jayadevan
>>
>>
>>
>>
>>
>> DISCLAIMER:
>>
>> "The information in this e-mail and any attachment is intended only for
>> the person to whom it is addressed and may contain confidential and/or
>> privileged material. If you have received this e-mail in error, kindly
>> contact the sender and destroy all copies of the original communication. IBS
>> makes no warranty, express or implied, nor guarantees the accuracy, adequacy
>> or completeness of the information contained in this email or any attachment
>> and is not liable for any errors, defects, omissions, viruses or for
>> resultant loss or damage, if any, direct or indirect."
>>
>>
>>
>>
>>
>

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Tomas Vondra 2011-08-31 11:41:55 Re: Query performance issue
Previous Message Jayadevan M 2011-08-31 11:19:37 Re: Query performance issue