Im proposing this change to /src/port/getaddrinfo.c
to support IPv6 under windows.
10a11,14
* Windows may or may not have these
routines, so we handle Windows special
* by dynamically checking for their existence.
If they already exist, we
* use the Windows native routines, but if
Im proposing this change to /src/port/getaddrinfo.c
to support IPv6 under windows.
(this time with a context diff !)
*** \postgresql-snapshot\src\port\getaddrinfo.c Wed
Aug 24 11:54:09 2005
--- \postgresql-patched\src\port\getaddrinfo.c Wed
Aug 24 11:53:05 2005
***
***
Jelinek; pgsql-patches@postgresql.org;
dpage@vale-housing.co.uk;
Bruce Momjian; Chuck McDevitt
Subject: Re: [HACKERS] Proposed patch to getaddrinfo.c to support
Tom Lane wrote:
Petr Jelinek [EMAIL PROTECTED] writes:
Yep those changes proposed in my previous email fixes IPv4 too
to figure out a way to update the patch...
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 25, 2005 2:51 PM
To: Petr Jelinek
Cc: Andrew Dunstan; pgsql-patches@postgresql.org; [EMAIL PROTECTED]
housing.co.uk; Bruce Momjian; Chuck McDevitt
Subject: Re
I've done a similar thing myself (building the complete backend with
Visual Studio 2005). I got it to basically work, but stopped due to
lack of interest in the PostgreSQL community.
But, I'd be happy to help out your effort in any way I can.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Monday, April 24, 2006 1:57 PM
To: Magnus Hagander
Cc: Chuck McDevitt; pgsql-patches@postgresql.org
Subject: Re: [PATCHES] Building with Visual C++
Magnus Hagander [EMAIL PROTECTED] writes:
The main difference between what I'm trying now from most of what
I've
People seem to be confusing sector size and cluster size.
Microsoft Windows assumes sectors are 8k or less on hard drives (99% are
512 bytes).
Cluster size is the allocation unit. On windows, this can be 512 to
256k (max 64k with 512 byte sectors).
NTFS (which I think we need) is limited to
with ntfs source that it
requires sector size = page size.
So on both systems, sectors can't be more than 4096.
Also, see http://support.microsoft.com/kb/923332
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chuck McDevitt
Sent: Tuesday, January 16, 2007 11:09
Win32 exception codes start with a two-bit severity indication.
00 means success, so nothing is wrong.
01 is an informational messages.
10 is a warning message.
11 is an error.
That's why the common exception codes you see start with hex C0, as they
are errors.
The rest of the top 16 bits are
Neil Conway [EMAIL PROTECTED] writes:
I don't see a reason to reject the patch. All the arguments about
why
using C++ in the backend is ill-advised are well-taken, but the
patch
does *not* require making a real commitment to making C++ usable as
a
backend extension language, it just
BTW, one problem I didn't understand at all was that g++ spit up on
bitand() and bitor() as function names. Those are not C++ keywords
to my knowledge; anyone have a theory?
I forgot these c++ keywords, as you never need to use them in a c++
program:
and bitand compl not_eq
11 matches
Mail list logo
