Re: Many Pl/PgSQL parameters -> AllocSetAlloc(128)?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: reuven(at)lerner(dot)co(dot)il, pgsql-general(at)postgresql(dot)org, "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Many Pl/PgSQL parameters -> AllocSetAlloc(128)?
Date: 2003-06-24 14:13:06
Message-ID: 19095.1056463986@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers pgsql-patches

Joe Conway <mail(at)joeconway(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Kallol Nandi 2003-06-24 14:14:38 Message at the console
Previous Message Tom Lane 2003-06-24 13:59:06 Re: [GENERAL] interesting PHP/MySQL thread

Browse pgsql-hackers by date

  From Date Subject
Next Message Larry Rosenman 2003-06-24 14:23:08 Re: interval's and printing...
Previous Message Tom Lane 2003-06-24 14:03:08 Re: a problem with index and user define type

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2003-06-24 14:45:50 Re: ecpg compile (compatlib)
Previous Message Jason Tishler 2003-06-24 13:51:54 Re: ecpg compile (compatlib)