| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Add PGAPPICON to all executable makefiles.
|
|
My initial impression that glibc was measuring the precision in characters
(which is what the Linux man page says it does) was incorrect. It does take
the precision to be in bytes, but it also tries to truncate the string at a
character boundary. The bottom line remains the same: it will mess up
if the string is not in the encoding it expects, so we need to avoid %.*s
anytime there's a significant risk of that. Previous code changes are still
good, but adjust the comments to reflect this knowledge. Per research by
Hernan Gonzalez.
|
|
Depending on which spec you read, field widths and precisions in %s may be
counted either in bytes or characters. Our code was assuming bytes, which
is wrong at least for glibc's implementation, and in any case libc might
have a different idea of the prevailing encoding than we do. Hence, for
portable results we must avoid using anything more complex than just "%s"
unless the string to be printed is known to be all-ASCII.
This patch fixes the cases I could find, including the psql formatting
failure reported by Hernan Gonzalez. In HEAD only, I also added comments
to some places where it appears safe to continue using "%.*s".
|
|
user and password can also be "".
|
|
This is mostly to suppress compiler warnings, although in principle
the cases could result in undesirable behavior.
Martin Pitt
|
|
Fujii Masao
|
|
there was an error processing the input file.
Work done by Zoltan.
|
|
|
|
corrupted. This error, however, does is not a compilation problem but a runtime
one, so we can keep compiling but still have to declare ERROR.
|
|
we get an error message instead of a warning if the variable have different types.
|
|
hides a global one with the same name.
|
|
ecpg.
|
|
GCC 4.5 complained about it.
|
|
files instead of relative ones which break vpath builds.
|
|
command.
Informix allows variables as argument to the embedded SQL command FREE. Given
that we only allow freeing cursors via FREE for compatibility reasons only we
should do the same.
|
|
ecpglib.
|
|
refactored the debug output wasn't adjusted.
|
|
commandline option "-i". This change fixes this and adds a test case. It also
honors #include_next, although this is probably never used for embedded SQL.
|
|
declare section.
|
|
|
|
Add ERRCODE_INVALID_PASSWORD sqlstate error code.
|
|
these definitions unique, too. It used to use the linenumber but in the rare case of two definitions in one line this was not unique.
|
|
|
|
the GSSAPI libraries crash.
Noted by Zdenek Kotala
|
|
error sqlstate. This change makes it return a correct value..
|
|
set ferror() but never set feof(). This is known to be the case for recent
glibc when trying to read a directory as a file, and might be true for other
platforms/cases too. Per report from Ed L. (There is more that we ought to
do about his report, but this is one easily identifiable issue.)
|
|
|
|
the fact that NetBSD/mips is currently broken, as per buildfarm member pika.
Also add regression tests to ensure that get_float8_nan and get_float4_nan
are exercised even on platforms where they are not needed by
float8in/float4in.
Zoltán Böszörményi and Tom Lane
|
|
regession test output, and update pgindent script to avoid them in the
future.
|
|
|
|
|
|
(hope I got 'em all). Per discussion, this release will be 9.0 not 8.5.
|
|
is invisible in psql, other interfaces, like libpq, make this value
visible.
Boszormenyi Zoltan
|
|
By Zoltán Böszörményi
|
|
just trying to figure out the minimal amount of defines needed.
|
|
If expand_dbname is non-zero and dbname contains an = sign, it is taken as
a conninfo string in exactly the same way as if it had been passed to
PQconnectdb. This is equivalent to the way PQsetdbLogin() works, allowing
PQconnectdbParams() to be a complete alternative.
Also improve the way the new function is called from psql and replace a
previously missed call to PQsetdbLogin() in psql. Additionally use
PQconnectdbParams() for pg_dump and friends, and the bin/scripts
command line utilities such as vacuumdb, createdb, etc.
Finally, update the documentation for the new parameter, as well as the
nuances of precedence in cases where key words are repeated or duplicated
in the conninfo string.
|
|
<float.h>' as well.
|
|
fixing yet another incorrect log output.
|
|
test failures on some architectures.
By Zoltán Böszörményi.
|
|
machines are all rejecting isinf() calls in this file.
|
|
making it OS independant.
Patch done by Zoltán Böszörményi.
|
|
order
so regression testing is possible,
by Zoltan Boszormenyi
|
|
reverse yes and no.
|
|
PQconnectStartParams. These are analogous to PQconnectdb and PQconnectStart
respectively. They differ from the legacy functions in that they accept
two NULL-terminated arrays, keywords and values, rather than conninfo
strings. This avoids the need to build the conninfo string in cases
where it might be inconvenient to do so. Includes documentation.
Also modify psql to utilize PQconnectdbParams rather than PQsetdbLogin.
This allows the new config parameter application_name to be set, which
in turn is displayed in the pg_stat_activity view and included in CSV
log entries. This will also ensure both new functions get regularly
exercised.
Patch by Guillaume Lelarge with review and minor adjustments by
Joe Conway.
|
|
of my commit.
|
|
cursor support to native mode.
|
|
|
|
auto-prepare mode if the connection is closed and re-opened and the previously prepared query is issued again.
|
|
|
