RE: [HACKERS] Bug report for 7.0beta1 in 'CREATE FUNCTION...'

From: Karel Zak - Zakkr <zakkr(at)zf(dot)jcu(dot)cz>
To: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
Cc: The Hermit Hacker <scrappy(at)hub(dot)org>, pgsql-hackers(at)postgreSQL(dot)org
Subject: RE: [HACKERS] Bug report for 7.0beta1 in 'CREATE FUNCTION...'
Date: 2000-03-01 10:38:08
Message-ID: Pine.LNX.3.96.1000301112834.29986C-100000@ara.zf.jcu.cz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Wed, 1 Mar 2000, Hiroshi Inoue wrote:

> > -----Original Message-----
> > From: owner-pgsql-hackers(at)postgresql(dot)org
> > [mailto:owner-pgsql-hackers(at)postgresql(dot)org]On Behalf Of The Hermit
> > Hacker
> >
> >
> > Can someone look into this, and followup with Don? :)
> >
>
> Currently utility commands aren't executable in PL/pgSQL.
> In short,it's due the lack of implementation of copyObject()
> for UtilityStatements.
> However,there's another essential problem.

Hmm, I see that copyObject() and freeObject() is really problematic
routines.

> PL/pgSQL caches prepared plans for fucntions at their
> first execution time. Though many oids/numbers ... exist
> in the cached plans,they are changed by DML statements
> and cached plans would become invalid. Currently once
> a plan is cached,it stays in TopMemoryContext forever
> and would never be removed/changed.

.. another TopMemoryContext feeder :-) The solution is
context-per-plan cache and small change in SPI (SPI_freeplan..).

I believe that it (SPI) will fixed in any next release.

Karel

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jose Soares 2000-03-01 12:22:23 Re: [HACKERS] having and union in v7beta
Previous Message Karel Zak - Zakkr 2000-03-01 10:14:12 Re: [HACKERS] Re: [PATCHES] NO-CREATE-TABLE and NO-LOCK-TABLE