| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
provide a macro so code can still just say qsort). Avoids linker warnings
on pickier platforms such as Darwin, and outright failure on MSVC.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
repeatedly. Now that we don't have to worry about memory leaks from
glibc's qsort, we can safely put CHECK_FOR_INTERRUPTS into the tuplesort
comparators, as was requested a couple months ago. Also, get rid of
non-reentrancy and an extra level of function call in tuplesort.c by
providing a variant qsort_arg() API that passes an extra void * argument
through to the comparison routine. (We might want to use that in other
places too, I didn't look yet.)
|
| |
|
|
|
| |
declared in the system headers. Per report from Bruce than some BSDen
are like this.
|
| |
|
|
| |
work around that with defines.
|
| |
|
|
|
| |
available directly on the platform. Per discussion, this function is
sufficiently widely recognized to be treated as standard.
|
| |
|
|
|
|
|
|
|
| |
return true for exactly the characters treated as whitespace by their flex
scanners. Per report from Victor Snezhko and subsequent investigation.
Also fix a passel of unsafe usages of <ctype.h> functions, that is, ye olde
char-vs-unsigned-char issue. I won't miss <ctype.h> when we are finally
able to stop using it.
|
| |
|
|
|
| |
path.c does not in itself force linking of both exec.c and libintl.
Should fix current ecpglib build failure on pickier platforms.
|
| |
|
|
|
| |
and other special flags on Windows. May fix intermittent 'Permission
denied' errors. Magnus Hagander
|
| |
|
|
| |
Magnus.
|
| | |
|
| |
|
|
| |
header files.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
After updating to the latest cvs, and also building most of the addons
(like PLs), the following patch is neededf for win32 + Visual C++.
* Switch to use the new win32 semaphore code
* Rename win32_open to pgwin32_open. win32_open collides with symbols
defined in Perl. MingW didn't detect ig, MSVC did. And it's a bit too
generic a name to export globally, imho...
* Python defines some partially broken #pragmas in the headers when
doing a debug build. Workaround.
Magnus Hagander
|
| |
|
|
|
|
|
|
|
|
| |
o remove many WIN32_CLIENT_ONLY defines
o add WIN32_ONLY_COMPILER define
o add 3rd argument to open() for portability
o add include/port/win32_msvc directory for
system includes
Magnus Hagander
|
| |
|
|
| |
Mark Morgan Lloyd
|
| | |
|
| |
|
|
| |
variable.
|
| | |
|
| |
|
|
| |
Backpatch to 8.1.X.
|
| | |
|
| |
|
|
|
| |
on libintl which may or may not provide what we need. Make a few marginal
cleanups to ensure this works. Andrew Dunstan and Tom Lane.
|
| | |
|
| |
|
|
|
|
|
| |
relocated after installation. We can't trust the installation paths
inserted into Makefile.global by configure, so instead we must get the
paths from pg_config. This requires extending pg_config to support all
the separately-configurable path names, but that was on TODO anyway.
|
| |
|
|
|
| |
it can be done right. Allow explicit use of absolute DataDir path.
Per Dave Page.
|
| |
|
|
|
| |
this was harder than it seemed at first glance). Also push code for
checking for ".." in file names into path.c where it belongs.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
of special case for Windows port. Put a PG_TRY around most of createdb()
to ensure that we remove copied subdirectories on failure, even if the
failure happens while creating the pg_database row. (I think this explains
Oliver Siegmar's recent report.) Having done that, there's no need for
the fragile assumption that copydir() mustn't ereport(ERROR), so simplify
its API. Eliminate the old code that used system("cp ...") to copy
subdirectories, in favor of using copydir() on all platforms. This not
only should allow much better error reporting, but allows us to fsync
the created files before trusting that the copy has succeeded.
|
| | |
|
| |
|
|
| |
build of zic.
|
| | |
|
| |
|
|
|
| |
some security issues, and upstream has declared it "dead". Patch from
Magnus Hagander, minor editorialization from Neil Conway.
|
| |
|
|
| |
them, the executation behavior could be unexpected.
|
| |
|
|
|
|
| |
should work on Windows now. Also, rename set_noblock to pg_set_noblock;
since it is included in libpq, the former name polluted application
namespace.
|
| |
|
|
| |
Add support for snprintf '+', 'h', and %* length settings.
|
| |
|
|
|
|
|
| |
Document use of macros for pg_printf functions.
Bump major versions of all interfaces to handle movement of get_progname
from libpq to libpgport in 8.0, and probably other libpgport changes in 8.1.
|
| |
|
|
|
| |
implementation doesn't export out via libpq and get used by a user
application.
|
| |
|
|
| |
Magnus Hagander
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
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 ...
|
| | |
|
| | |
|
| |
|
|
|
|
| |
everywhere not just some places, get rid of . and .. when joining path
sections together. This should eliminate most of the ugly paths like
/foo/bar/./baz that we've been generating.
|
| |
|
|
| |
don't support junction points. Doesn't affect native Win32.
|
| |
|
|
|
|
| |
+ #if defined(_MSC_VER) || defined(__BORLANDC__)
+ #define WIN32_CLIENT_ONLY
+ #endif
|
| |
|
|
| |
rename prototype conflict.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Fix TablespaceCreateDbspace() to be able to create a dummy directory
in place of a dropped tablespace's symlink. This eliminates the open
problem of a PANIC during WAL replay when a replayed action attempts
to touch a file in a since-deleted tablespace. It also makes for a
significant improvement in the usability of PITR replay.
|
| | |
|