| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Backpatch to 8.2.X.
L Bayuk
|
| | |
|
| |
|
|
| |
back-stamped for this.
|
| | |
|
| | |
|
| |
|
|
| |
Per Thorkil Olesen.
|
| |
|
|
| |
an = sign. Tom Lane and Andrew Dunstan.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
FormatMessage() (This should have been in 8.2.0, patched to 8.2.X and
HEAD):
I think this problem to be complex....
http://archives.postgresql.org/pgsql-hackers/2006-11/msg00042.php
FormatMessage of windows cannot consider the encoding of the database.
However, I should try the solution now. It is necessary to clear the
problem.
Multi character-code exists together in message and log. It doesn't
consider
the data base encoding that the user intended....
The user in multi-byte country can try this.
http://inet.winpg.jp/~saito/pg_bug/MessageCheck.c
That is, it is likely to become it in this manner.(Japanese)
http://inet.winpg.jp/~saito/pg_bug/FormatMessage998.png
Hiroshi Saito
|
| | |
|
| | |
|
| |
|
|
|
| |
some of the Windows-only makefiles; the correct place to assert these
things is pg_config.h.win32. Per bug #2677.
|
| |
|
|
|
|
|
| |
Negotiation failure is only likely to happen if one side or the other is
misconfigured, eg. bad client certificate. I'm not 100% convinced that
a retry is really the best thing, hence not back-patching this fix for now.
Per gripe from Sergio Cinos.
|
| | |
|
| |
|
|
| |
Hiroshi Saito
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
which turns out to be a dominant part of the runtime in scenarios
involving lots of parse-time warnings (such as Stephen Frost's example
of an INSERT with a lot of backslash-containing strings). There's not
a whole lot we can do about the character-at-a-time scanning, but we
can at least avoid traversing the query twice.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
per Magnus.
|
| |
|
|
|
| |
than before. Albe Laurenz (but editorialized heavily by me, so if it
doesn't work it's my fault).
|
| | |
|
| | |
|
| |
|
|
|
| |
to allow obtaining information about previously prepared statements and
open cursors. Volkan Yazici
|
| |
|
|
|
|
| |
_CRT_SECURE_NO_DEPRECATE.
Hiroshi Saito
|
| | |
|
| |
|
|
| |
Hiroshi Saito
|
| |
|
|
| |
pg-specific code in those files, or might be some day.
|
| |
|
|
| |
Albe Laurenz
|
| |
|
|
|
|
|
|
| |
"DESCRIPTION", which is actually only allowed for device drivers. The
compilers ignore it with a warning - if we remove them, we get rid of
the warning.
Magnus Hagander
|
| | |
|
| | |
|
| |
|
|
|
| |
have no other gods before c.h'. Also remove some demonstrably redundant
#include lines, mostly of <errno.h> which was added to c.h years ago.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
fe-auth.c:573: warning: passing argument 1 of 'free' discards qualifiers
from pointer target type
pg_krb5_authname used to return a (const char *) to memory allocated by
krb. Somewhere along the lines this was changed so that a copy was
made, returned, and freed instead. However the const modifier was never
removed.
|
| | |
|
| | |
|
| |
|
|
| |
Christopher Kings-Lynne
|
| |
|
|
|
|
|
|
|
| |
libpq/md5.h, so that there's a clear separation between backend-only
definitions and shared frontend/backend definitions. (Turns out this
is reversing a bad decision from some years ago...) Fix up references
to crypt.h as needed. I looked into moving the code into src/port, but
the headers in src/include/libpq are sufficiently intertwined that it
seems more work than it's worth to do that.
|
| |
|
|
|
|
|
| |
the lower-level large object functions fails, it will have already set
a suitable error message --- probably something from the backend ---
and it is not useful to overwrite that with a generic 'error while
reading large object' message. So remove redundant messages.
|
| |
|
|
| |
Problems noted while experimenting with new control-C code for psql.
|
| |
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
| |
Backpatch to 8.1.X.
|
| | |
|
| |
|
|
| |
wasn't exported by exports.txt. Ooops. Per buildfarm results.
|
| |
|
|
|
|
|
|
|
| |
and standard_conforming_strings; likewise for the other client programs
that need it. As per previous discussion, a pg_dump dump now conforms
to the standard_conforming_strings setting of the source database.
We don't use E'' syntax in the dump, thereby improving portability of
the SQL. I added a SET escape_strings_warning = off command to keep
the dumps from getting a lot of back-chatter from that.
|
| |
|
|
|
|
|
| |
Per Coverity bug #304. Thanks to Martijn van Oosterhout for reporting it.
Zero out the pointer fields of PGresult so that these mistakes are more
easily catched, per discussion.
|
| | |
|