- 06 1月, 2005 14 次提交
-
-
由 Dennis Bjorklund 提交于
-
由 Dennis Bjorklund 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
consistent. On Unix we now always consult getpwuid(); $HOME isn't used at all. On Windows the code currently consults $USERPROFILE, or $HOME if that's not defined, but I expect this will change as soon as the win32 hackers come to a consensus. Nothing done yet about changing the file names used underneath $USERPROFILE.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 05 1月, 2005 5 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
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.
-
由 Tom Lane 提交于
Michael Fuhr.
-
由 Peter Eisentraut 提交于
dangling cross-references.
-
由 Peter Eisentraut 提交于
-
- 04 1月, 2005 13 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
< * 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.
-
由 Bruce Momjian 提交于
> 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.
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
Viktor Vislobokov
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
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.
-
- 03 1月, 2005 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> * Allow building with directories containing spaces
-
- 02 1月, 2005 5 次提交
-
-
由 Tom Lane 提交于
the src/tools/copyright script.
-
由 Tom Lane 提交于
should have been caught by the src/tools/copyright script ... why weren't they?
-
由 Bruce Momjian 提交于
< the Win32 wcscoll() can be used. > the Win32 wcscoll() can be used, and perhaps other functions > like towupper().
-
由 Bruce Momjian 提交于
< the Win32 strcoll() can be used. > the Win32 wcscoll() can be used.
-
由 Bruce Momjian 提交于
< 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.
-
- 01 1月, 2005 1 次提交
-
-
由 Bruce Momjian 提交于
-