| Commit message (Collapse) | Author | Age |
|
|
|
| |
Per email from Craig Ringer
|
| |
|
|
|
|
| |
commit-fest.
|
|
|
|
| |
Postgres 9.2, and perhaps no existing users either.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove the following ports:
- dgux
- nextstep
- sunos4
- svr4
- ultrix4
- univel
These are obsolete and not worth rescuing. In most cases, there is
circumstantial evidence that they wouldn't work anymore anyway.
|
|
|
|
| |
Josh Kupershmidt
|
|
|
|
| |
Brar Piening, reviewed by Craig Ringer.
|
|
|
|
|
|
|
| |
Original patch by Lars Kanis, reviewed by Nishiyama Tomoaki and tweaked some by me.
This compiler, or at least the latest version of it, is currently broken, and
only passes the regression tests if built with -O0.
|
|
|
|
|
|
| |
This reverts commit 52d01c2f52c462d29ae0fdfa44c3cae129148a6d.
the UINT64_FORMAT bit broke the b uildfarm, so I'm reverting the whole thing pending further investigation.
|
|
|
|
|
| |
Both this and "%lld" work, but the compiler's format checking doesn't
like "%lld", so we get all sorts of spurious warnings.
|
|
|
|
| |
Mostly to do with macro redefinitions or object signedness.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These functions should take a pg_locale_t, not a collation OID, and should
call mbstowcs_l/wcstombs_l where available. Where those functions are not
available, temporarily select the correct locale with uselocale().
This change removes the bogus assumption that all locales selectable in
a given database have the same wide-character conversion method; in
particular, the collate.linux.utf8 regression test now passes with
LC_CTYPE=C, so long as the database encoding is UTF8.
I decided to move the char2wchar/wchar2char functions out of mbutils.c and
into pg_locale.c, because they work on wchar_t not pg_wchar_t and thus
don't really belong with the mbutils.c functions. Keeping them where they
were would have required importing pg_locale_t into pg_wchar.h somehow,
which did not seem like a good plan.
|
|
|
|
| |
Per buildfarm.
|
| |
|
|
|
|
|
| |
There is not yet support in initdb to populate the pg_collation
catalog, but if that is done manually, the rest should work.
|
| |
|
|
|
|
|
|
| |
This can be used to build 64 bit Windows binaries, not only on 64 bit
Windows but on supported cross-compiling hosts including 32 bit Windows,
Cygwin, Darwin and Linux.
|
|
|
|
|
|
|
|
|
|
| |
Add support for collecting "minidump" style crash dumps on
Windows, by setting up an exception handling filter. Crash
dumps will be generated in PGDATA/crashdumps if the directory
is created (the existance of the directory is used as on/off
switch for the generation of the dumps).
Craig Ringer and Magnus Hagander
|
|
|
|
|
|
| |
(Hm, I wonder whether BCC defines them either...)
Also label dangling endifs a bit better in this area.
|
|
|
|
|
|
| |
My previous patch exposed the fact that we didn't have these. Those
hard-wired octal constants were actually wrong on Windows, not just
inconsistent.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Recent versions of the Linux system header files cause xlogdefs.h to
believe that open_datasync should be the default sync method, whereas
formerly fdatasync was the default on Linux. open_datasync is a bad
choice, first because it doesn't actually outperform fdatasync (in fact
the reverse), and second because we try to use O_DIRECT with it, causing
failures on certain filesystems (e.g., ext4 with data=journal option).
This part of the patch is largely per a proposal from Marti Raudsepp.
More extensive changes are likely to follow in HEAD, but this is as much
change as we want to back-patch.
Also clean up confusing code and incorrect documentation surrounding the
fsync_writethrough option. Those changes shouldn't result in any actual
behavioral change, but I chose to back-patch them anyway to keep the
branches looking similar in this area.
In 9.0 and HEAD, also do some copy-editing on the WAL Reliability
documentation section.
Back-patch to all supported branches, since any of them might get used
on modern Linux versions.
|
|
|
|
|
| |
by gcc version 4 on mingw and cygwin. We don't use dllexport here
because dllexport and dllwrap don't work well together.
|
| |
|
|
|
|
| |
with Magnus's script to remove these.
|
| |
|
|
|
|
|
| |
but is __declspec (dllimport) on other compilers
because cygwin and mingw don't like dllexport.
|
|
|
|
| |
independently from BUILDING_DLL. It is always __declspec(dllexport).
|
|
|
|
|
|
|
|
|
| |
and use this in pq_getbyte_if_available.
It's only a limited implementation which swithes the whole emulation layer
no non-blocking mode, but that's enough as long as non-blocking is only
used during a short period of time, and only one socket is accessed during
this time.
|
|
|
|
|
|
|
|
|
| |
compilers, by applying a configure check to see if the compiler will accept
an unreferenced "static inline foo ..." function without warnings. It is
believed that such warnings are the only reason not to declare inlined
functions in headers, if the compiler understands "inline" at all.
Kurt Harriman
|
|
|
|
|
|
|
| |
the server.
Gets rid of a fairly ugly hack for Solaris, and also provides hostname
and IPV6 support.
|
|
|
|
| |
members complaining.
|
| |
|
|
|
|
| |
IPV6 headers in newer SDKs.
|
|
|
|
|
|
|
|
|
|
| |
that memory allocated by starting third party DLLs doesn't end up
conflicting with it.
Hopefully this solves the long-time issue with "could not reattach
to shared memory" errors on Win32.
Patch from Tsutomu Yamada and me, based on idea from Trevor Talbot.
|
|
|
|
| |
provided by Andrew.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Also, if linked against other versions than the default MSVCRT library
(for example the MSVC build which links against MSVCRT80), also update
the cache in the default MSVCRT at the same time.
This should fix the issues with setting LC_MESSAGES on the MSVC build.
Original patch from Hiroshi Inoue and Hiroshi Saito, much rewritten
by me.
|
| |
|
|
|
|
|
| |
header file. SunOS 4 is probably broken anyway, but this item stuck out as
completely weird.
|
|
|
|
|
|
|
|
|
|
| |
This particular batch was just for *.c and *.h file.
The changes were made with the following 2 commands:
find . \( \( -name 'libstemmer' -o -name 'expected' -o -name 'ppport.h' \) -prune \) -o \( -name '*.[ch]' \) \( -exec grep -q '\$PostgreSQL' {} \; -o -print \) | while read file ; do head -n 1 < $file | grep -q '^/\*' && echo $file; done | xargs -l sed -i -e '1s/^\// /' -e '1i/*\n * $PostgreSQL:$ \n *'
find . \( \( -name 'libstemmer' -o -name 'expected' -o -name 'ppport.h' \) -prune \) -o \( -name '*.[ch]' \) \( -exec grep -q '\$PostgreSQL' {} \; -o -print \) | xargs -l sed -i -e '1i/*\n * $PostgreSQL:$ \n */'
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
data structures and backend internal APIs. This solves problems we've seen
recently with inconsistent layout of pg_control between machines that have
32-bit time_t and those that have already migrated to 64-bit time_t. Also,
we can get out from under the problem that Windows' Unix-API emulation is not
consistent about the width of time_t.
There are a few remaining places where local time_t variables are used to hold
the current or recent result of time(NULL). I didn't bother changing these
since they do not affect any cross-module APIs and surely all platforms will
have 64-bit time_t before overflow becomes an actual risk. time_t should
be avoided for anything visible to extension modules, however.
|
|
|
|
| |
builds of libpq in both 32 and 64-bit. Per gripe from Hiroshi Saito.
|
|
|
|
|
|
| |
used when building addons.
Dave Page
|
| |
|
| |
|
| |
|
|
|
|
| |
for this.
|
|
|
|
|
|
|
|
| |
childprocess deaths instead of using one thread per child. This drastastically
reduces the address space usage and should allow for more backends running.
Also change the win32_waitpid functionality to use an IO Completion Port for
queueing child death notices instead of using a fixed-size array.
|
|
|
|
| |
third party includes (like tcl) that define DLLIMPORT.
|
|
|
|
|
| |
by dynamically loading the function that's missing from the MingW
headers and library.
|