Re: Do we really want to migrate plproxy and citext intoPG core distribution? - Mailing list pgsql-hackers

From Marko Kreen
Subject Re: Do we really want to migrate plproxy and citext intoPG core distribution?
Date
Msg-id e51f66da0807280541i43552887p34c2f4ff6b2a5d69@mail.gmail.com
Whole thread Raw
In response to Re: Do we really want to migrate plproxy and citext intoPG core distribution?  ("Hiroshi Saito" <z-saito@guitar.ocn.ne.jp>)
Responses Re: Do we really want to migrate plproxy and citext intoPG core distribution?  ("Marko Kreen" <markokr@gmail.com>)
List pgsql-hackers
On 7/25/08, Hiroshi Saito <z-saito@guitar.ocn.ne.jp> wrote:
>  I tackled with hope temporarily. It seems that some adjustment is still
> required.
>  http://winpg.jp/~saito/pg_work/plproxy/
>  However, windows user desires to use. Of course, it is also me.
>  Regards,
>  Hiroshi Saito

Thanks, I applied the patch to CVS, with minor changes:
- Use HAVE_SYS_SELECT_H instead of WIN32 for <sys/select.h>
- Do SHLIB_LINK += instead of separate var.

Could you please test the attached patch or CVS HEAD,
whether everything works fine now?

Btw, do not worry about regtest failure in plproxy_many,
this is due to differences in system random() function.
The test should rewritten, although I have not yet decided how...

--
marko

Attachment

pgsql-hackers by date:

Previous
From: Dave Cramer
Date:
Subject: Re: Protocol 3, Execute, maxrows to return, impact?
Next
From: "Marko Kreen"
Date:
Subject: Re: Do we really want to migrate plproxy and citext intoPG core distribution?