[Bug 230615] New: Postgresql 8.1 does not work with Python 2.5
https://bugzilla.novell.com/show_bug.cgi?id=230615 Summary: Postgresql 8.1 does not work with Python 2.5 Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: SuSE Other Status: NEW Severity: Blocker Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: dieter.leinweber@d-leinweber.de QAContact: qa@suse.de The Postgresql version 8.1.5 shipped with OpenSuse 10.2 does not work with Python 2.5. As a result any stored procedure that uses plpythonu procedural (and there plpy) language will crash. This bug has been confirmed by the Postgresql team and was solved in the new version 8.2. To make Postgresql working on OpenSuse 10.2 without having the need to compile ist from scratch the new version should be made available as an update asap. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=230615 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |max@novell.com |screening@forge.provo.novell| |.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=230615 max@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Blocker |Normal Status|NEW |NEEDINFO Info Provider| |dieter.leinweber@d-leinweber.de ------- Comment #1 from max@novell.com 2007-01-02 02:09 MST ------- I can't release an update to PostgreSQL 8.2 for openSUSE 10.2, as our policy is to (almost) never make major version updates for packages on released products. However there is an inofficial update available on ftp://ftp.suse.com/pub/projects/postgresql/postgresql-8.2.0 . But be aware that applications from 10.2 that are linked against libpq will conflict with the new packages, as the soname of libpq has been bumped for 8.2. Is updating to 8.2 the only fix the PostgreSQL team offers for this, or will it also be addressed in a 8.1.6 release? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=230615 ------- Comment #2 from dieter.leinweber@d-leinweber.de 2007-01-02 05:09 MST ------- I'm not an insider on PostgreSQL, but the web site http://www.postgresql.org currently does not make any announcement of a version 8.1.6. I don't even know wether the PostgreSQL-team considers 8.2.0 a new major version update (which imho would have version 9). When I'm thinking back there was always a very tight relationship between the PostgreSQL version and the Python version needed to use plpythonu and - to my knowledge - there was never a compatibility version of an "old" PostgreSQL version to support a "new" Python version (imho Python 2.3 was used for PostgreSQL 8.0.x and there was never a PostgreSQL 8.0.x that supported Python 2.4). I can live with that unofficial update and will test it in the next few days. There are ready made RPMs for Fedora which includes a Compat-RPM that provides the "old" libpq. If I get time I will test this RPM. Anyone who uses PostgreSQL with plpythonu will have to avoid using SuSE 10.2 or have to update one of the two components (and Python has a LOT of dependencies), therefore the easiest way to do this is to update PostgreSQL... For me a complete set og inofficial updates (including a Compat-RPM) would do the job. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=230615 ------- Comment #3 from max@novell.com 2007-01-02 05:38 MST ------- (In reply to comment #2)
I'm not an insider on PostgreSQL, but the web site http://www.postgresql.org currently does not make any announcement of a version 8.1.6.
I didn't say there is a version 8.1.6. My question was whether the source where you learned about the problem being fixed in 8.2 maybe also said that it will be fixed in the 8.1 series as well with the next minor release (which would be 8.1.6).
I don't even know wether the PostgreSQL-team considers 8.2.0 a new major version update (which imho would have version 9).
The PostgreSQL team counts differently than most others. They call a change in the second position (e.g. 8.1 to 8.2) a major release, which among other things means, that the on-disk file format isn't compatible between one and the other.
When I'm thinking back there was always a very tight relationship between the PostgreSQL version and the Python version needed to use plpythonu and - to my knowledge - there was never a compatibility version of an "old" PostgreSQL version to support a "new" Python version (imho Python 2.3 was used for PostgreSQL 8.0.x and there was never a PostgreSQL 8.0.x that supported Python 2.4).
Frankly, for me, this would be a reason to avoid using Python as a PL in PostgreSQL. Just as an example, the Tcl community goes long ways to ensure binary compatibility back and forth over many releases back to the late 90s. But I'll see what I can do to get it working in 10.2. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=230615 ------- Comment #4 from dieter.leinweber@d-leinweber.de 2007-01-09 02:27 MST ------- Python is easy to learn and works under Windows as well without having the need to recompile stuff (as it would be if I would write the stored procedures in C). Postgresql is not the only software where I have to take care of version numbers, therefore that's not an issue for me. In the meantime I've installed the "unofficial" updates and now everything works as expected. It seems that the "old" libpq ist still available and that "old" applications (quickly tested with pgaccess) still work. That's fine! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=230615 max@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|dieter.leinweber@d- | |leinweber.de | Resolution| |WONTFIX ------- Comment #5 from max@novell.com 2007-04-26 11:21 MST ------- OK, as it works for you and nobody else complained, I'll leave it to the upstream projects to sort out their incompatibilities. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com