- 26 9月, 2011 1 次提交
-
-
由 Tom Lane 提交于
The keywords and values arguments of these functions are more properly declared "const char * const *" than just "const char **". Lionel Elie Mamane, reviewed by Craig Ringer
-
- 24 9月, 2011 1 次提交
-
-
由 Magnus Hagander 提交于
This mode still exists for backwards compatibility, making sslmode=require the same as sslmode=verify-ca when the file is present, but not causing an error when it isn't. Per bug 6189, reported by Srinivas Aji
-
- 07 9月, 2011 2 次提交
-
-
由 Bruce Momjian 提交于
Per Peter.
-
由 Bruce Momjian 提交于
pgpass. Backpatch to 9.1.
-
- 05 7月, 2011 1 次提交
-
-
由 Magnus Hagander 提交于
Per bug #6089, noted by Sidney Cadot
-
- 29 6月, 2011 1 次提交
-
-
由 Peter Eisentraut 提交于
We had previously (af26857a) established the U.S. spellings as standard.
-
- 19 6月, 2011 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 01 6月, 2011 1 次提交
-
-
由 Tom Lane 提交于
It turns out the reason we hadn't found out about the portability issues with our credential-control-message code is that almost no modern platforms use that code at all; the ones that used to need it now offer getpeereid(), which we choose first. The last holdout was NetBSD, and they added getpeereid() as of 5.0. So far as I can tell, the only live platform on which that code was being exercised was Debian/kFreeBSD, ie, FreeBSD kernel with Linux userland --- since glibc doesn't provide getpeereid(), we fell back to the control message code. However, the FreeBSD kernel provides a LOCAL_PEERCRED socket parameter that's functionally equivalent to Linux's SO_PEERCRED. That is both much simpler to use than control messages, and superior because it doesn't require receiving a message from the other end at just the right time. Therefore, add code to use LOCAL_PEERCRED when necessary, and rip out all the credential-control-message code in the backend. (libpq still has such code so that it can still talk to pre-9.1 servers ... but eventually we can get rid of it there too.) Clean up related autoconf probes, too. This means that libpq's requirepeer parameter now works on exactly the same platforms where the backend supports peer authentication, so adjust the documentation accordingly.
-
- 19 5月, 2011 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 05 5月, 2011 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 03 5月, 2011 1 次提交
-
-
由 Alvaro Herrera 提交于
Greg Smith
-
- 08 4月, 2011 1 次提交
-
-
由 Tom Lane 提交于
As noted by Thom Brown, this confuses the DocBook index processor; it fails to merge entries that differ only in whitespace, and sorts them unexpectedly as well. Seems like a toolchain bug, but I'm not going to hold my breath waiting for a fix. Note: easiest way to find these is to look for double spaces in HTML.index.
-
- 12 3月, 2011 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
for consistency.
-
- 11 3月, 2011 1 次提交
-
-
由 Bruce Momjian 提交于
to fully process errors.
-
- 19 2月, 2011 1 次提交
-
-
由 Peter Eisentraut 提交于
Add a new libpq connection option client_encoding (which includes the existing PGCLIENTENCODING environment variable), which besides an encoding name accepts a special value "auto" that tries to determine the encoding from the locale in the client's environment, using the mechanisms that have been in use in initdb. psql sets this new connection option to "auto" when running from a terminal and not overridden by setting PGCLIENTENCODING. original code by Heikki Linnakangas, with subsequent contributions by Jaime Casanova, Peter Eisentraut, Stephen Frost, Ibrar Ahmed
-
- 13 2月, 2011 3 次提交
-
-
由 Bruce Momjian 提交于
format. Modify PQescapeStringConn() docs to be consisent with other escaping functions. Add mention problems with pre-9.0 versions of libpq using not understanding bytea hex format to the 9.0 release notes. Backpatch to 9.0 docs.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 07 2月, 2011 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
using an itemized list.
-
- 05 2月, 2011 1 次提交
-
-
由 Bruce Momjian 提交于
libpq doc mentions.
-
- 03 2月, 2011 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 30 1月, 2011 1 次提交
-
-
由 Bruce Momjian 提交于
capitalization.
-
- 18 1月, 2011 1 次提交
-
-
由 Bruce Momjian 提交于
Ray Stell Also fix some libpq title capitalization problems.
-
- 14 1月, 2011 1 次提交
-
-
由 Bruce Momjian 提交于
by Robert Haas.
-
- 13 1月, 2011 1 次提交
-
-
由 Bruce Momjian 提交于
reviewed by Robert Haas.
-
- 29 12月, 2010 1 次提交
-
-
由 Tom Lane 提交于
It must be added at the end of the ExecStatusType enum to avoid ABI breakage compared to previous libpq versions. Noted by Magnus.
-
- 27 12月, 2010 1 次提交
-
-
由 Alvaro Herrera 提交于
-
- 22 12月, 2010 1 次提交
-
-
由 Magnus Hagander 提交于
This function is like the PQserverVersion() function except it returns the version of libpq, making it possible for a client program or driver to determine which version of libpq is in use at runtime, and not just at link time. Suggested by Harald Armin Massa and several others.
-
- 11 12月, 2010 1 次提交
-
-
由 Robert Haas 提交于
Fujii Masao. Review by Alvaro Herrera, Tom Lane, and myself.
-
- 27 11月, 2010 2 次提交
-
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
Basically, we want to distinguish all cases where the connection was not made from those where it was. A convenient proxy for this is to see if we got a message with a SQLSTATE code back from the postmaster. This presumes that the postmaster will always send us a SQLSTATE in a failure message, which is true for 7.4 and later postmasters in every case except fork failure. (We could possibly complicate the postmaster code to do something about that, but it seems not worth the trouble, especially since pg_ctl's response for that case should be to keep waiting anyway.) If we did get a SQLSTATE from the postmaster, there are basically only two cases, as per last week's discussion: ERRCODE_CANNOT_CONNECT_NOW and everything else. Any other error code implies that the postmaster is in principle willing to accept connections, it just didn't like or couldn't handle this particular request. We want to make a special case for ERRCODE_CANNOT_CONNECT_NOW so that "pg_ctl start -w" knows it should keep waiting. In passing, pick names for the enum constants that are a tad less likely to present collision hazards in future.
-
- 26 11月, 2010 1 次提交
-
-
由 Bruce Momjian 提交于
status, including a status where the server is running but refuses a postgres connection. Have pg_ctl use this new function. This fixes the case where pg_ctl reports that the server is not running (cannot connect) but in fact it is running.
-
- 25 11月, 2010 1 次提交
-
-
由 Bruce Momjian 提交于
supplied, also print the IP address. This allows IPv4 and IPv6 failures to be distinguished. Also useful when a hostname resolves to multiple IP addresses. Also, remove use of inet_ntoa() and use our own inet_net_ntop() in all places, including in libpq, because it is thread-safe.
-
- 24 11月, 2010 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 22 10月, 2010 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 21 9月, 2010 1 次提交
-
-
由 Magnus Hagander 提交于
-
- 29 8月, 2010 1 次提交
-
-
由 Tom Lane 提交于
Spotted by Dmitriy Igrishin. Back-patch to 8.2, which is when the PREPARE statement was improved to allow parameter types to be omitted.
-
- 17 8月, 2010 1 次提交
-
-
由 Peter Eisentraut 提交于
-