Skip site navigation (1) Skip section navigation (2)

Re: PL/Python warnings in CVS HEAD

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Marko Kreen <markokr(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Neil Conway <neilc(at)samurai(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PL/Python warnings in CVS HEAD
Date: 2007-04-03 13:36:30
Message-ID: 200704031336.l33DaVY15579@momjian.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Great.  Care to take on the Python boolean patch?

      o Allow PL/PythonU to return boolean rather than 1/0

        http://archives.postgresql.org/pgsql-patches/2007-01/msg00596.php


It requires only a few lines of code, but some testing, which you seem
to have available.

---------------------------------------------------------------------------

Marko Kreen wrote:
> On 4/3/07, Marko Kreen <markokr(at)gmail(dot)com> wrote:
> > On 4/3/07, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > > Where are we on Python 2.5?
> >
> > I'll look into it.
> 
> Following patch converts plpython.c to use Python 2.5 types,
> with compat ifdef for older version.  This is recommended
> method by PEP 353 to fix the issue.
> 
> Tested with python 2.4.3, 2.5.
> 
> -- 
> marko

[ Attachment, skipping... ]

> 
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>        choose an index scan if your joining column's datatypes do not
>        match

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>          http://momjian.us
  EnterpriseDB                               http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2007-04-03 13:37:24
Subject: Re: PL/Python warnings in CVS HEAD
Previous:From: Bruce MomjianDate: 2007-04-03 13:33:23
Subject: Re: scan_recycle_buffers

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group