| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |
|
|
|
|
| |
The previous patches failed to cover a lot of symlinks that are only
added in platform-specific cases. Make the lists match what's in the
Makefile for each branch.
|
| |
|
|
| |
Backpatch to 8.2 as that's how far the structure looks the same.
|
| | |
|
| | |
|
| |
|
|
| |
with Magnus's script to remove these.
|
| |
|
|
|
|
| |
ecpg also does not regard cursor names as case-sensitive.
Thanks to Zoltan Boszormenyi for the patch.
|
| |
|
|
| |
at end of files.
|
| | |
|
| |
|
|
|
|
| |
I just noticed that libpq's pqsignal.h was violating our general inclusion
style guidelines by explicitly including postgres_fe.h. Remove that, and
put it in pqsignal.c where it belongs.
|
| |
|
|
|
|
|
|
| |
interval input "invalid" was specified together with other fields. Spotted
by Neil Conway with the help of a clang warning. Although this has been
wrong since the interval code was written more than 10 years ago, it doesn't
affect anything beyond which error message you get for a wrong input, so not
worth back-patching very far.
|
| |
|
|
| |
Per buildfarm, again.
|
| |
|
|
| |
per report from Dave Page
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
This adds a libpq connection parameter requirepeer that specifies the user
name that the server process is expected to run under.
reviewed by KaiGai Kohei
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
parameter against server cert's CN field) to succeed in the case where
both host and hostaddr are specified. As with the existing precedents
for Kerberos, GSSAPI, SSPI, it is the calling application's responsibility
that host and hostaddr match up --- we just use the host name as given.
Per bug #5559 from Christopher Head.
In passing, make the error handling and messages for the no-host-name-given
failure more consistent among these four cases, and correct a lie in the
documentation: we don't attempt to reverse-lookup host from hostaddr
if host is missing.
Back-patch to 8.4 where SSL cert verification was introduced.
|
| | |
|
| |
|
|
| |
(And there was much rejoicing.)
|
| | |
|
| |
|
|
|
| |
SIO_KEEPALIVE_VALS define instead of just WIN32, since MingW doesn't
support this API (yet?).
|
| |
|
|
| |
libpq support.
|
| |
|
|
|
|
| |
MacOS X uses TCP_KEEPALIVE rather than TCP_KEEPIDLE for this purpose.
Thanks to Fujii Masao for the review.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
linking both executables and shared libraries, and we add on LDFLAGS_EX when
linking executables or LDFLAGS_SL when linking shared libraries. This
provides a significantly cleaner way of dealing with link-time switches than
the former behavior. Also, make sure that the various platform-specific
%.so: %.o rules incorporate LDFLAGS and LDFLAGS_SL; most of them missed that
before. (I did not add these variables for the platforms that invoke $(LD)
directly, however. It's not clear if we can do that safely, since for the
most part we assume these variables use CC command-line syntax.)
Per gripe from Aaron Swenson and subsequent investigation.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds four additional connection parameters to libpq: keepalives,
keepalives_idle, keepalives_count, and keepalives_interval.
keepalives default to on, per discussion, but can be turned off by
specifying keepalives=0. The remaining parameters, where supported,
can be used to adjust how often keepalives are sent and how many
can be lost before the connection is broken.
The immediate motivation for this patch is to make sure that
walreceiver will eventually notice if the master reboots without
closing the connection cleanly, but it should be helpful in other
cases as well.
Tollef Fog Heen, Fujii Masao, and me.
|
| |
|
|
|
| |
constant format strings, so that the compiler can more easily check the
formats for correctness.
|
| |
|
|
|
|
|
| |
While the values were correctly returned they were not moved into C variables
as they should be.
Closes: #5489
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
"val AS name" to "name := val", as per recent discussion.
This patch catches everything in the original named-parameters patch,
but I'm not certain that no other dependencies snuck in later (grepping
the source tree for all uses of AS soon proved unworkable).
In passing I note that we've dropped the ball at least once on keeping
ecpg's lexer (as opposed to parser) in sync with the backend. It would
be a good idea to go through all of pgc.l and see if it's in sync now.
I didn't attempt that at the moment.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
additional cases correctly. The original coding failed to load additional
(chain) certificates from the client cert file, meaning that indirectly signed
client certificates didn't work unless one hacked the server's root.crt file
to include intermediate CAs (not the desired approach). Another problem was
that everything got loaded into the shared SSL_context object, which meant
that concurrent connections trying to use different sslcert settings could
well fail due to conflicting over the single available slot for a keyed
certificate.
To fix, get rid of the use of SSL_CTX_set_client_cert_cb(), which is
deprecated anyway in the OpenSSL documentation, and instead just
unconditionally load the client cert and private key during connection
initialization. This lets us use SSL_CTX_use_certificate_chain_file(),
which does the right thing with additional certs, and is lots simpler than
the previous hacking about with BIO-level access. A small disadvantage is
that we have to load the primary client cert a second time with
SSL_use_certificate_file, so that that one ends up in the correct slot
within the connection's SSL object where it can get paired with the key.
Given the other overhead of making an SSL connection, that doesn't seem
worth worrying about.
Per discussion ensuing from bug #5468.
|
| | |
|
| |
|
|
| |
'AC_TYPE_LONG_LONG_INT' macro call.
|
| |
|
|
| |
in ecpg and replaces the old test that was kind of hackish.
|
| |
|
|
| |
used to cover the equally long "long long" type. This patch closes bug #5464.
|
| | |
|
| |
|
|
| |
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.
|
