subroutine that can hide platform dependencies.  The WIN32 path is still
a stub, but I await a fix from one of the win32 hackers.
Also clean up unnecessary #ifdef WIN32 ugliness in a couple of places.

Michael Fuhr.

dangling cross-references.

< * Allow building with directories containing spaces
> * Allow building in directories containing spaces
<   There are two capabilities here, first the ability to build from a
<   source directory that contains spaces, and second the ability to install
<   into a directory that contains spaces.  The first is probably not
<   possible because 'gmake' and other compiler tools do not fully support
<   spaces in path names.  The second is possible with proper quoting in
<   the makefiles.  Because PostgreSQL supports relocatable installs, it
<   is possible to install into a directory that doesn't contain spaces and
<   then copy the install to a directory with spaces.
>   This is probably not possible because 'gmake' and other compiler tools
>   do not fully support quoting of paths with spaces.
>
> * Allow installing to directories containing spaces
>
>   This is possible if proper quoting is added to the makefiles for the
>   install targets.  Because PostgreSQL supports relocatable installs, it
>   is already possible to install into a directory that doesn't contain
>   spaces and then copy the install to a directory with spaces.

>   There are two capabilities here, first the ability to build from a
>   source directory that contains spaces, and second the ability to install
>   into a directory that contains spaces.  The first is probably not
>   possible because 'gmake' and other compiler tools do not fully support
>   spaces in path names.  The second is possible with proper quoting in
>   the makefiles.  Because PostgreSQL supports relocatable installs, it
>   is possible to install into a directory that doesn't contain spaces and
>   then copy the install to a directory with spaces.

 Viktor Vislobokov

share lock on a buffer being written out before releasing BufMgrLock in
the BufferAlloc code path; if we do it later we might block on someone
who's re-pinned the buffer.  I believe this is only an issue for BufferAlloc
and not the other places that call FlushBuffer.  BufferSync must continue
to do it the old way since it may well be trying to write buffers that
other backends have pinned; but it should not be holding any conflicting
locks.  FlushRelationBuffers is okay since it's got exclusive lock at the
relation level.

> * Allow building with directories containing spaces

the src/tools/copyright script.

should have been caught by the src/tools/copyright script ... why
weren't they?

< 	  the Win32 wcscoll() can be used.
> 	  the Win32 wcscoll() can be used, and perhaps other functions
> 	  like towupper().

< 	  the Win32 strcoll() can be used.
> 	  the Win32 wcscoll() can be used.

<         o Disallow encodings like UTF8 which which PostgreSQL supports
>         o Disallow encodings like UTF8 which PostgreSQL supports
914a915,917
>
> 	  To fix UTF8, the data needs to be converted to UTF16 and then
> 	  the Win32 strcoll() can be used.

forgot to autoconf after tag'ng configure.in with rc3

Tag appropriate files for rc3

Also performed an initial run through of upgrading our Copyright date to
extend to 2005 ... first run here was very simple ... change everything
where: grep 1996-2004 && the word 'Copyright' ... scanned through the
generated list with 'less' first, and after, to make sure that I only
picked up the right entries ...

to put more widely useful info before less widely useful info.

overlooked in 7.3 updates.  Not a critical fix but avoids a notice when
the resulting SQL script is executed.

to shared memory as soon as possible, ie, right after read_backend_variables.
The effective difference from the original code is that this happens
before instead of after read_nondefault_variables(), which loads GUC
information and is apparently capable of expanding the backend's memory
allocation more than you'd think it should.  This should fix the
failure-to-attach-to-shared-memory reports we've been seeing on Windows.
Also clean up a few bits of unnecessarily grotty EXEC_BACKEND code.