Peter Eisentraut wrote:
> Bruce Momjian wrote:
> > I thought about that. The docs were pointing to an FAQ number that
> > doesn't exit anymore, and there is text indicating sometimes the
> > shared compile isn't needed, so I didn't want to hard-code a version
> > number in case it wasn't significant aoyway. And if I say newer, it
> > will be not-newer in a few years. :-)
>
> If you say "x or newer" then that will be true forever unless they take
> it back out. We should also try to figure out a way for people to find
> out how their python was compiled rather than making them compile a new
> one.
>
> I would prefer to put more effort into giving people a procedure to
> follow during PostgreSQL installation to verify the correct setup of
> their system, rather than giving them a bunch of options to "try" when
> they have unidentified "problems".
I can confirm it was added in 2.3:
http://www.python.org/doc/current/whatsnew/node20.html
Docs updated:
If you have problems, run Python 2.3 or later's configure using the
<literal>--enable-shared</> flag. On some operating systems you
don't have to build a shared library, but you will have
to convince the <productname>PostgreSQL</> build system of this.
Consult the <filename>Makefile</filename> in the
<filename>src/pl/plpython</filename> directory for details.
--
Bruce Momjian | http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
