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

Re: plperl doc update

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: PostgreSQL-documentation <pgsql-docs(at)postgresql(dot)org>
Subject: Re: plperl doc update
Date: 2004-02-26 23:17:51
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-docs
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 

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

In response to


pgsql-docs by date

Next:From: Bruce MomjianDate: 2004-02-27 00:36:14
Subject: Re: plperl doc update
Previous:From: Bruce MomjianDate: 2004-02-26 23:06:00
Subject: Re: plperl doc update

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