2011/6/19 Robert Haas robertmh...@gmail.com:
On Sat, Jun 18, 2011 at 9:21 AM, Pavel Stehule pavel.steh...@gmail.com
wrote:
Is this profile expected?
I've certainly seen profiles before where the catcache overhead was
significant. I don't think that I've seen SearchCatCache() quite this
2011/6/19 Pavel Stehule pavel.steh...@gmail.com:
2011/6/19 Robert Haas robertmh...@gmail.com:
On Sat, Jun 18, 2011 at 9:21 AM, Pavel Stehule pavel.steh...@gmail.com
wrote:
Is this profile expected?
I've certainly seen profiles before where the catcache overhead was
significant. I don't
Hello
I tried to optimize repeated assign in plpgsql with elimination
unnecessary palloc/free calls.
I tested changes on simple bublesort
postgres=# \sf buble
CREATE OR REPLACE FUNCTION public.buble(integer[])
RETURNS integer[]
LANGUAGE plpgsql
AS $function$
declare
unsorted bool := true;
On Sat, Jun 18, 2011 at 9:21 AM, Pavel Stehule pavel.steh...@gmail.com wrote:
Is this profile expected?
I've certainly seen profiles before where the catcache overhead was
significant. I don't think that I've seen SearchCatCache() quite this
high on any of the profiling I've done, but then
