Re: Why performance improvement on converting subselect to a function ?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Rajesh Kumar Mallah <mallah(at)trade-india(dot)com>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-performance(at)postgresql(dot)org, "Shridhar Daithankar" <shridhar_daithankar(at)persistent(dot)co(dot)in>
Subject: Re: Why performance improvement on converting subselect to a function ?
Date: 2003-07-30 13:51:23
Message-ID: 9198.1059573083@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Rajesh Kumar Mallah <mallah(at)trade-india(dot)com> writes:
> What lead to degradation was the bumping off of
> effective_cache_size parameter from 1000 to 64K

Check the plan then; AFAIR the only possible effect of changing
effective_cache_size is to influence which plan the planner picks.

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Shridhar Daithankar 2003-07-30 13:56:48 Re: Why performance improvement on converting subselect to a function ?
Previous Message Rajesh Kumar Mallah 2003-07-30 07:24:49 Re: Why performance improvement on converting subselect to a function ?