OK, lets talk portability.

From: mlw <markw(at)mohawksoft(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: OK, lets talk portability.
Date: 2002-05-07 12:42:15
Message-ID: 3CD7CBA7.111B8720@mohawksoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

As I set out to do the Windows semaphore thing, I notice it can get quite ugly.

In the current CVS directory, there is pgsql/src/backend/port directory.

I propose that this become a separate subproject and library. The reason I want
this is because the semaphore support, specifically multiple semaphores
identified by a single key, has to be implemented with shared memory and
multiple semaphores. (Under Windows)

I also have to look at "ownership" issues with Windows processes and shared
objects. They may need to be own be a more persistent/independent module, a
DLL.

By creating a library like "libpgport.a" (or on Windows pgport.dll/pgport.lib)
little has to be changed for various ports. If we don't have the library then
the discrete object filed would need to be specified. The library will give the
port writer a greater amount of flexibility.

Comments?

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-05-07 13:11:53 Re: Schemas: status report, call for developers
Previous Message Matthew Kirkwood 2002-05-07 11:15:32 Re: HEADS UP: Win32/OS2/BeOS native ports