Re: information Windows - PostgreSQL - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: information Windows - PostgreSQL
Date
Msg-id 303E00EBDD07B943924382E153890E5433F886@cuthbert.rcsinc.local
Whole thread Raw
In response to information Windows - PostgreSQL  ("P.M" <pmdanger@yahoo.com>)
Responses Re: information Windows - PostgreSQL  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Outside of some quirky behavior like int/0 handling, what is wrong with
the peerdirect's signal handler so that it has to be redone?  Win32 has
signal handling, just not as robust and complete as *nix.

Regards,
Merlin

-----Original Message-----
From: Bruce Momjian [mailto:pgman@candle.pha.pa.us]
Sent: Wednesday, June 18, 2003 10:03 AM
To: P.M
Cc: PostGreSQL mailing list
Subject: Re: [HACKERS] information Windows - PostgreSQL


Not sure.  We are petty deep in the backend code allowing CreateProcess
and then we need to add signal handling.  We don't have anything running
yet.


------------------------------------------------------------------------
---

P.M wrote:
> Hi,
>
> I would like to participate to PostgreSQL under
> Windows platform.
>
> What can i do to help ?
>
> x04001
>
> __________________________________
> Do you Yahoo!?
> SBC Yahoo! DSL - Now only $29.95 per month!
> http://sbc.yahoo.com
>
> ---------------------------(end of
broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if
your
>       joining column's datatypes do not match
>

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (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 7: don't forget to increase your free space map settings


pgsql-hackers by date:

Previous
From: Andreas Pflug
Date:
Subject: Re: pg_get_triggerdef in pg_dump
Next
From: Rod Taylor
Date:
Subject: Re: pg_get_triggerdef in pg_dump