Re: [GENERAL] Many Pl/PgSQL parameters -> AllocSetAlloc(128)? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [GENERAL] Many Pl/PgSQL parameters -> AllocSetAlloc(128)?
Date
Msg-id 19095.1056463986@sss.pgh.pa.us
Whole thread Raw
In response to Re: [GENERAL] Many Pl/PgSQL parameters -> AllocSetAlloc(128)?  (Joe Conway <mail@joeconway.com>)
List pgsql-hackers
Joe Conway <mail@joeconway.com> writes:
> Actually, adding a "pfree(oneres);" to the end of that for loop plugs
> the memory leak and allows me to see the error message:

Good catch.

> Takes a while to check all 16777216 possibilities though, so I'm still
> not sure more isn't needed here.

I wonder why it's doing anything at all --- the check for supertypes
ought to trigger only for complex type (rowtype) arguments, and there
are none here.

            regards, tom lane

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: a problem with index and user define type
Next
From: Larry Rosenman
Date:
Subject: Re: interval's and printing...