Re: pl/python do not delete function arguments

From: Jan Urbański <wulczer(at)wulczer(dot)org>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com>, Postgres - Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pl/python do not delete function arguments
Date: 2011-02-26 18:13:24
Message-ID: 1298744004.10781.2.camel@Nokia-N900-42-11
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > > On Tue, Feb 15, 2011 at 6:04 PM, Jan Urbański <wulczer(at)wulczer(dot)org>
> > > wrote:
> > > > On 15/02/11 20:39, Peter Eisentraut wrote:
> > > > > On tis, 2011-02-15 at 09:58 +0100, Jan Urbański wrote:
> > > > > > [a bug that we don't know how to fix]
> >
> > > From this discussion I gather that we have a problem here that we
> > > don't exactly know how to fix, so I'm inclined to suggest that we
> > > mark this Returned with Feedback in the CommitFest and instead add
> > > it to the TODO.   Since this is a pre-existing bug and not a new
> > > regression, it should not be something we hold up beta for.
> >
> > I'm officially at a loss on how to fix that bug without some serious
> > gutting of how PL/Python arguments work. If someone comes up with a
> > brilliant way to solve this problem, we can commit it after beta, or
> > even during the 9.2 cycle (should the brilliant solution be
> > backpatcheable).
>
> Is this discussion related to the following todo item:
>
> Create a new restricted execution class that will allow passing
> function arguments in as locals. Passing them as globals means
> functions cannot be called recursively.

Yep, the bug it's more or less an emanation of this problem.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nick Raj 2011-02-26 18:43:12 Spatio-Temporal Functions
Previous Message PostgreSQL - Hans-Jürgen Schönig 2011-02-26 18:12:42 Re: WIP: cross column correlation ...