Due to time constraints, I do not directly answer general PostgreSQL
questions. For assistance, please join the appropriate mailing list and
post your question:
You can also try the #postgresql IRC channel. See the PostgreSQL FAQ
for more information.
> See attached for a small patch that enables plpython to build cleanly
> under Cygwin. This patch together with my previous Python patch:
> enables full Python support (i.e., configure --with-python) for Cygwin
> See below for some more details and one issue.
> On Mon, May 14, 2001 at 10:26:39AM -0400, Jason Tishler wrote:
> > On Fri, May 11, 2001 at 03:54:06AM +0200, Ernesto Revilla wrote:
> > > now I did it, so I wanted to ask
> > > 1. if somebody could merge my makefile with the original one
> > > 2. put the plpython into the postgres source tree 'pl' (as experimental or
> > > whatever)
> > It appears that plpython was recently (i.e., 2001/05/09) added to
> > PostgreSQL CVS. So the above is not necessary.
> > However, a small patch is necessary for plpython to build cleanly under
> > Cygwin. Please get the latest PostgreSQL from CVS and apply the
> > attached patch. I ran the supplied test.sh and all tests passed with
> > the exception of the oid related ones (which is to be expected).
> > I would be very interested to hear if plpython works for you in a real
> > application, so please let me know.
> > I intend improve my patch as follows:
> > 1. add -DUSE_DL_IMPORT to CPPFLAGS in a cleaner way
> I moved this hunk from src/pl/plpython/Makefile to
> src/makefiles/Makefile.win to help keep all (well most) of the Win32
> crud in one place.
> > 2. deal with the different socket module name in Python 1.5.x and 2.x,
> > if possible
> My patch contains a hunk for src/pl/plpython/feature.expected since
> Python 2.1's underlying socket (shared extension) module is "_socket"
> instead of "socket". I guess one could have two different
> feature.expected files, one for each version, but I wasn't sure that it
> was worth the effort.
> > I will also test it out on a non-Cygwin platform to make sure that I
> > didn't break anything on a UNIX platform.
> I tested the patch under Linux without any ill effects.
> > Once the above is completed, I will submit the patch to pgsql-patches
> > for consideration.
> Jason Tishler
> Director, Software Engineering Phone: +1 (732) 264-8770 x235
> Dot Hill Systems Corp. Fax: +1 (732) 264-8798
> 82 Bethany Road, Suite 7 Email: Jason(dot)Tishler(at)dothill(dot)com
> Hazlet, NJ 07730 USA WWW: http://www.dothill.com
[ Attachment, skipping... ]
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
In response to
pgsql-cygwin by date
|Next:||From: Jason Tishler||Date: 2001-05-25 15:26:07|
|Subject: Updated: postgresql-7.1.1-1|
|Previous:||From: Jason Tishler||Date: 2001-05-24 13:50:18|
|Subject: Re: Python/Postgres Pygres for Win32 w/o cygwin|
pgsql-patches by date
|Next:||From: Bruce Momjian||Date: 2001-05-24 16:54:06|
|Subject: Re: Cygwin python and plpython patches|
|Previous:||From: Bruce Momjian||Date: 2001-05-24 16:53:12|
|Subject: Re: Cygwin PostgreSQL Python Module Patch|