|
1 |
| -<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.279 2009/03/23 01:45:29 momjian Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.280 2009/03/28 01:36:11 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="libpq">
|
4 | 4 | <title><application>libpq</application> - C Library</title>
|
@@ -6169,11 +6169,13 @@ myEventProc(PGEventId evtId, void *evtInfo, void *passThrough)
|
6169 | 6169 | </para>
|
6170 | 6170 |
|
6171 | 6171 | <para>
|
6172 |
| - If you are using <acronym>SSL</> inside your application (in addition |
6173 |
| - to inside <application>libpq</application>), you can call |
6174 |
| - <function>PQinitSSL(int)</> with <literal>0</> to tell |
6175 |
| - <application>libpq</application> that the <acronym>SSL</> library |
6176 |
| - has already been initialized by your application. |
| 6172 | + If your application initializes <literal>libssl</> or |
| 6173 | + <literal>libcrypto</> libraries and <application>libpq</application> |
| 6174 | + is built with <acronym>SSL</> support, you should call |
| 6175 | + <function>PQinitSSL(0)</> to tell <application>libpq</application> |
| 6176 | + that the <literal>libssl</> and <literal>libcrypto</> libraries |
| 6177 | + have been initialized by your application so |
| 6178 | + <application>libpq</application> will not initialize those libraries. |
6177 | 6179 | <!-- If this URL changes replace it with a URL to www.archive.org. -->
|
6178 | 6180 | See <ulink
|
6179 | 6181 | url="http://h71000.www7.hp.com/doc/83final/BA554_90007/ch04.html"></ulink>
|
|