Re: [Pypgsql-users] Which sourcefiles needed?

[Dick K. <d.j...@ch...>]

Op do 24-04-2003, om 14:53 schreef Gerhard Haering:
> Dick Kniep wrote:
> > Hi list,
> > 
> > We are developing a system with a central database and many clients. The
> > server and all clients run Linux. The database runs on the central
> > server (surprise, surprise). To run pyPgSQL on the clients, we need to
> > install it on all clients (is that so?), but to compile it (on the
> > client), it needs Postgresql files. My question is which files are
> > needed, and where should I locate them...
> 
> I can't tell which files exactly are needed to build against 
> PostgreSQL's libpq. Building pyPgSQL works best if you have the 
> PostgreSQL header and libraries installed (and not just in a PostgreSQL 
> source tree). For most Linux distributions, there are several PostgreSQL 
> packages, in particular you'll need the development package.
> 
> It's called postgresql-dev under Debian and has similar names under the 
> other distributions.
> 
> The correct paths should be picked up by setup.py automatically for most 
> major distributions (Debian, SuSE, Redhat). If not, you'll have to fire 
> up an editor with setup.py and
> 
> - set USE_CUSTOM = 1
> - set include_dirs and library_dirs appropriately
> 
> HTH,
> 
> -- Gerhard
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Pypgsql-users mailing list
> Pyp...@li...
> https://lists.sourceforge.net/lists/listinfo/pypgsql-users

Thanks for the advice, I am using Slackware, which is a bit different
from Redhat and others. I see 3 alternatives:

- Compile on the server and also RUN on the server, in which case I will
have to adjust the PYTHONPATH on the client (is that the only required
change?? and is it performing??)
- Compile on the server (which has all files naturally) and distribute
libpq etc. to the clients
- Compile on the clients after installing Postgresql completely (Ugly)

Both from a performance and maintainance point of view I would prefer
the first option, but do not know exactly how to go about it.
Maintainance off course because there is only one installation of the
package, which is always easier to maintain.
I think it is also on the performance side the best option, as it
processes all actual I/O and conversion on the server, and passes only
the results back to the client, only the actual import of the package
requires extra network traffic.

Kind regards,
Dick Kniep