Current Win32 port status

Lists: pgsql-hackerspgsql-hackers-win32
From: Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com>
To: "'pgsql-hackers-win32(at)postgresql(dot)org'" <pgsql-hackers-win32(at)postgresql(dot)org>
Cc: "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org>
Subject: Current Win32 port status
Date: 2003-12-21 05:25:20
Message-ID: A02DEC4D1073D611BAE8525405FCCE2B0280A0@harris.memetrics.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers pgsql-hackers-win32


Hi all,

just a small note to anyone who is interested in the status of this port.

Firstly, the fork/exec changes are coming along well. The first patch, for
fork/exec'ing of backends has been accepted and applied. A second patch, for
fork/exec'ing of the remainder of the postgres process has just been
submitted for review. Two patches (which are essentially already completed)
will follow this; the first to allow some further rearrangement of the
postmaster fork/execs in preparation for the Win32 CreateProcess calls, and
the final patch will place the actual CreateProcess calls into the
code-base.

It is reasonable to expect that we will have this changes in place within a
few weeks.

At that point, we will be within striking distance of a Win32 port. The
"only" remaining barriers to a running, albeit "imperfect", implementation
are:
* signals (non-trivial, to say the least, but encouraging to see
discussion occurring in this regard),
* a workable pipe replacement
* possible bootstrap issue between semaphores + shared memory

[these, and other remaining issues to "perfect" the port, are listed in
greater detail on
http://momjian.postgresql.org/main/writings/pgsql/win32.html]

FWIW, having kludged up some quick + dirty workarounds to the above points,
I have actually had postgres running natively on my Win2K box, which I trust
is an encouraging sign (to say the least) to anyone hanging out for this
port...

Merry Chirstmas all,
Claudio

---
Certain disclaimers and policies apply to all email sent from Memetrics.
For the full text of these disclaimers and policies see
<a
href="http://www.memetrics.com/emailpolicy.html">http://www.memetrics.com/em
ailpolicy.html</a>


From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com>
Cc: "'pgsql-hackers-win32(at)postgresql(dot)org'" <pgsql-hackers-win32(at)postgresql(dot)org>, "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Current Win32 port status
Date: 2003-12-22 07:14:09
Message-ID: 200312220714.hBM7E9g24509@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers pgsql-hackers-win32

Claudio Natoli wrote:
>
> Hi all,
>
> just a small note to anyone who is interested in the status of this port.
>
> Firstly, the fork/exec changes are coming along well. The first patch, for
> fork/exec'ing of backends has been accepted and applied. A second patch, for
> fork/exec'ing of the remainder of the postgres process has just been
> submitted for review. Two patches (which are essentially already completed)
> will follow this; the first to allow some further rearrangement of the
> postmaster fork/execs in preparation for the Win32 CreateProcess calls, and
> the final patch will place the actual CreateProcess calls into the
> code-base.
>
> It is reasonable to expect that we will have this changes in place within a
> few weeks.
>
> At that point, we will be within striking distance of a Win32 port. The
> "only" remaining barriers to a running, albeit "imperfect", implementation
> are:
> * signals (non-trivial, to say the least, but encouraging to see
> discussion occurring in this regard),
> * a workable pipe replacement

I don't have 'pipe' mentioned on the win32 patch. Can you give details?

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073