database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-27 12:41:57 +03:00
Code Activity

Clean up some problems in new asynchronous-connection logic

Browse Source 
in libpq --- mostly, poor response to error conditions.  You now actually
get to see the postmaster's 'The Data Base System is starting up' message,
which you didn't before.  I suspect the SSL code is still broken though.
This commit is contained in:
Tom Lane
2000-01-14 05:33:15 +00:00
parent 0e6d72db55
commit 2af360ed1c
4 changed files with 160 additions and 178 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
doc/src/sgml/libpq.sgml
View File

@ -323,23 +323,12 @@ PostgresPollingStatusType *PQconnectPoll(PQconn *conn)
</listitem>
<listitem>
<para>
CONNECTION_AWAITING_RESPONSE: Waiting for a response from the backend.
CONNECTION_AWAITING_RESPONSE: Waiting for a response from the postmaster.
</para>
</listitem>
<listitem>
<para>
CONNECTION_AUTH_RESPONSE: Got an authentication response; about to deal
with it.
</para>
</listitem>
<listitem>
<para>
CONNECTION_ERROR_RESPONSE: Got an error response; about to deal with it.
</para>
</listitem>
<listitem>
<para>
CONNECTION_AUTH_OK: Received authentication; waiting for ReadyForQuery etc.
CONNECTION_AUTH_OK: Received authentication; waiting for backend startup.
</para>
</listitem>
<listitem>
@ -373,7 +362,7 @@ PostgresPollingStatusType *PQconnectPoll(PQconn *conn)
</para>
<para>
Note that if PQconnectStart returns a non-NULL pointer, you must call
PQfinish upon that, when you are finished with it, in order to dispose of
PQfinish when you are finished with it, in order to dispose of
the structure and any associated memory blocks. This must be done even if a
call to PQconnectStart or PQconnectPoll failed.
</para>