Re: pgsql: Fix for plpython functions; return true/false for boolean,

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Guido Goldstein <guido(dot)goldstein(at)a-nugget(dot)org>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pgsql: Fix for plpython functions; return true/false for boolean,
Date: 2007-02-20 03:49:27
Message-ID: 200702200349.l1K3nR522344@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers pgsql-patches


I am still waiting for a plpython patch that has Python version
checking.

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

Guido Goldstein wrote:
> Peter Eisentraut wrote:
> > Guido Goldstein wrote:
> >> Is it possible to tell me which python versions you want to
> >> support?
> >
> > The issue isn't so much which versions we want to support. There is
> > certainly some flexibility with that. But when a patch breaks the
> > buildfarm a) unannounced and b) without any apparent feature gain, then
> > people get annoyed.
>
> If this breaks the buildfarm it's not my failure.
> Except you can tell me what I've got to do with the
> buildfarm.
>
> If you mean that plpython didn't compile, fine; simply tell
> the people what version they should consider when sending
> in patches.
>
> I've checked the patch with postgres 8.1.3 and 8.2.1
> with python 2.4 and 2.5 on intel 32 bit and amd 64 bit
> systems; all systems running linux.
>
> *And* it's not a feature patch but a bug-fixing one!
> Python is a language with strong typing, so silently
> converting a datatype is a bug -- not a feature.
> Btw, you'll lose the type information of boolean columns in
> trigger functions (NEW and OLD dicts, no explicit parameters),
> which does cause problems.
>
> > That said, we certainly try to support a few more versions of Python
> [...]
>
> If you want to support python 2.3 use the attached patch, which also
> works for the newer python versions.
> The Python 2.3 branch is the oldest _officially_ supported python version.
>
> Anyway, to circumvent the above mentiond point a) I herewith anncounce
> that the included patch might break the buildfarm.
>
> Cheers
> Guido
>

>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings

--
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

Browse pgsql-committers by date

  From Date Subject
Next Message User Dpage 2007-02-20 08:59:54 pginstaller - pginst: Add LongName attribute for xxid.v80.sql, per
Previous Message Bruce Momjian 2007-02-20 03:47:03 pgsql: Remove item: < o ARRAY[[1, 2], [3, 4]])[1] should return the same

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Smith 2007-02-20 03:59:38 Log levels for checkpoint/bgwriter monitoring
Previous Message Tom Lane 2007-02-20 03:44:06 Re: [PATCHES] WIP patch - INSERT-able log statements

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2007-02-20 04:09:40 Re: [PATCHES] WIP patch - INSERT-able log statements
Previous Message Bruce Momjian 2007-02-20 03:47:23 Re: BUG #2913: Subscript on multidimensional array yields no value