- 04 9月, 2006 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 15 7月, 2006 1 次提交
-
-
由 Tom Lane 提交于
-
- 14 7月, 2006 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 12 5月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 06 5月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 27 4月, 2006 4 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
with be-secure.c.
-
由 Bruce Momjian 提交于
applications don't need the SSL headers. Martijn van Oosterhout
-
由 Bruce Momjian 提交于
In the SSL code in libpq it does some processing with DH parameters: SSL_CTX_set_tmp_dh_callback() This function is marked as server use only[1], the client always uses the DH parameters in the server, so all the code in the client dealing with the DH parameters is useless. This patch removes it. It's not clear why the code was added in the first place, it's been there almost since the beginning[2]. At the time there was a suggestion of merging the front-end and backend SSL code, but looking at the changes since, that seems unlikely. As a further example, the s_server program allows you to specify DH params, but s_client doesn't. In the GnuTLS documentation under gnutls_dh_params_generate2() it says[3]: Also note that the DH parameters are only useful to servers. Since clients use the parameters sent by the server, it's of no use to call this in client side.
-
- 05 3月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 25 1月, 2006 1 次提交
-
-
由 Tom Lane 提交于
provided by configure, instead. Per bug #2205.
-
- 24 10月, 2005 1 次提交
-
-
由 Bruce Momjian 提交于
PQregisterThreadLock(). I also remove the crypt() mention in the libpq threading section and added a single sentence in the client-auth manual page under crypt(). Crypt authentication is so old now that a separate paragraph about it seemed unwise. I also added a comment about our use of locking around pqGetpwuid().
-
- 15 10月, 2005 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 29 8月, 2005 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 24 8月, 2005 3 次提交
-
-
由 Bruce Momjian 提交于
Windows. The test itself is bypassed in configure as discussed, and libpq has been updated appropriately to allow it to build in thread-safe mode. Dave Page
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 10 1月, 2005 1 次提交
-
-
由 Tom Lane 提交于
since st_ino can't be trusted on that platform. Per report from T.J.
-
- 09 1月, 2005 1 次提交
-
-
由 Tom Lane 提交于
from our long-established standard.
-
- 07 1月, 2005 2 次提交
- 06 1月, 2005 1 次提交
-
-
由 Tom Lane 提交于
consistent. On Unix we now always consult getpwuid(); $HOME isn't used at all. On Windows the code currently consults $USERPROFILE, or $HOME if that's not defined, but I expect this will change as soon as the win32 hackers come to a consensus. Nothing done yet about changing the file names used underneath $USERPROFILE.
-
- 05 1月, 2005 1 次提交
-
-
由 Tom Lane 提交于
subroutine that can hide platform dependencies. The WIN32 path is still a stub, but I await a fix from one of the win32 hackers. Also clean up unnecessary #ifdef WIN32 ugliness in a couple of places.
-
- 01 1月, 2005 1 次提交
-
-
由 PostgreSQL Daemon 提交于
Tag appropriate files for rc3 Also performed an initial run through of upgrading our Copyright date to extend to 2005 ... first run here was very simple ... change everything where: grep 1996-2004 && the word 'Copyright' ... scanned through the generated list with 'less' first, and after, to make sure that I only picked up the right entries ...
-
- 03 12月, 2004 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
handling in SIGPIPE processing; avoid unnecessary pollution of application link-symbol namespace; spell 'pointer to function' in the conventional way.
-
- 02 12月, 2004 1 次提交
-
-
由 Bruce Momjian 提交于
calling applications. This is done by blocking sigpipe in the libpq thread and using sigpending/sigwait to possibily discard any sigpipe we generated.
-
- 20 11月, 2004 2 次提交
- 16 10月, 2004 1 次提交
-
-
由 Bruce Momjian 提交于
Magnus Hagander
-
- 28 9月, 2004 2 次提交
-
-
由 Bruce Momjian 提交于
structures plus pointers used by the structure.
-
由 Bruce Momjian 提交于
This greatly helps threaded libpq programs.
-
- 27 9月, 2004 1 次提交
-
-
由 Tom Lane 提交于
-
- 24 9月, 2004 1 次提交
-
-
由 Tom Lane 提交于
in open_client_SSL, surely we should do it everywhere. Also make message formatting conform to style guide.
-
- 23 9月, 2004 1 次提交
-
-
由 Bruce Momjian 提交于
stands a chance of looking it up. "Unrecognised error" is always disheartening. :-) Dominic Mitchell
-
- 29 8月, 2004 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 18 8月, 2004 1 次提交
-
-
由 Bruce Momjian 提交于
Always create thread-specific variable.
-