mirror of
https://github.com/postgres/postgres.git
synced 2025-06-26 12:21:12 +03:00
Remove tabs after spaces in C comments
This was not changed in HEAD, but will be done later as part of a pgindent run. Future pgindent runs will also do this. Report by Tom Lane Backpatch through all supported branches, but not HEAD
This commit is contained in:
Bruce Momjian
@ -134,7 +134,7 @@ static int ldapServiceLookup(const char *purl, PQconninfoOption *options,
|
||||
*
|
||||
* PQconninfoOptions[] is a constant static array that we use to initialize
|
||||
* a dynamically allocated working copy. All the "val" fields in
|
||||
* PQconninfoOptions[] *must* be NULL. In a working copy, non-null "val"
|
||||
* PQconninfoOptions[] *must* be NULL. In a working copy, non-null "val"
|
||||
* fields point to malloc'd strings that should be freed when the working
|
||||
* array is freed (see PQconninfoFree).
|
||||
* ----------
|
||||
@ -453,7 +453,7 @@ PQping(const char *conninfo)
|
||||
* See comment for PQconnectdbParams for the definition of the string format.
|
||||
*
|
||||
* Returns a PGconn*. If NULL is returned, a malloc error has occurred, and
|
||||
* you should not attempt to proceed with this connection. If the status
|
||||
* you should not attempt to proceed with this connection. If the status
|
||||
* field of the connection returned is CONNECTION_BAD, an error has
|
||||
* occurred. In this case you should call PQfinish on the result, (perhaps
|
||||
* inspecting the error message first). Other fields of the structure may not
|
||||
@ -528,7 +528,7 @@ PQconnectStartParams(const char **keywords,
|
||||
* See comment for PQconnectdb for the definition of the string format.
|
||||
*
|
||||
* Returns a PGconn*. If NULL is returned, a malloc error has occurred, and
|
||||
* you should not attempt to proceed with this connection. If the status
|
||||
* you should not attempt to proceed with this connection. If the status
|
||||
* field of the connection returned is CONNECTION_BAD, an error has
|
||||
* occurred. In this case you should call PQfinish on the result, (perhaps
|
||||
* inspecting the error message first). Other fields of the structure may not
|
||||
@ -810,14 +810,14 @@ connectOptions2(PGconn *conn)
|
||||
*
|
||||
* Parse an empty string like PQconnectdb() would do and return the
|
||||
* resulting connection options array, ie, all the default values that are
|
||||
* available from the environment etc. On error (eg out of memory),
|
||||
* available from the environment etc. On error (eg out of memory),
|
||||
* NULL is returned.
|
||||
*
|
||||
* Using this function, an application may determine all possible options
|
||||
* and their current default values.
|
||||
*
|
||||
* NOTE: as of PostgreSQL 7.0, the returned array is dynamically allocated
|
||||
* and should be freed when no longer needed via PQconninfoFree(). (In prior
|
||||
* and should be freed when no longer needed via PQconninfoFree(). (In prior
|
||||
* versions, the returned array was static, but that's not thread-safe.)
|
||||
* Pre-7.0 applications that use this function will see a small memory leak
|
||||
* until they are updated to call PQconninfoFree.
|
||||
@ -1433,7 +1433,7 @@ connectDBComplete(PGconn *conn)
|
||||
for (;;)
|
||||
{
|
||||
/*
|
||||
* Wait, if necessary. Note that the initial state (just after
|
||||
* Wait, if necessary. Note that the initial state (just after
|
||||
* PQconnectStart) is to wait for the socket to select for writing.
|
||||
*/
|
||||
switch (flag)
|
||||
@ -1495,7 +1495,7 @@ connectDBComplete(PGconn *conn)
|
||||
* will not block.
|
||||
* o If you do not supply an IP address for the remote host (i.e. you
|
||||
* supply a host name instead) then PQconnectStart will block on
|
||||
* gethostbyname. You will be fine if using Unix sockets (i.e. by
|
||||
* gethostbyname. You will be fine if using Unix sockets (i.e. by
|
||||
* supplying neither a host name nor a host address).
|
||||
* o If your backend wants to use Kerberos authentication then you must
|
||||
* supply both a host name and a host address, otherwise this function
|
||||
@ -1782,7 +1782,7 @@ keep_going: /* We will come back to here until there is
|
||||
/*
|
||||
* This connection failed --- set up error report, then
|
||||
* close socket (do it this way in case close() affects
|
||||
* the value of errno...). We will ignore the connect()
|
||||
* the value of errno...). We will ignore the connect()
|
||||
* failure and keep going if there are more addresses.
|
||||
*/
|
||||
connectFailureMessage(conn, SOCK_ERRNO);
|
||||
@ -2477,7 +2477,7 @@ keep_going: /* We will come back to here until there is
|
||||
/*
|
||||
* If we tried to send application_name, check to see
|
||||
* if the error is about that --- pre-9.0 servers will
|
||||
* reject it at this stage of the process. If so,
|
||||
* reject it at this stage of the process. If so,
|
||||
* close the connection and retry without sending
|
||||
* application_name. We could possibly get a false
|
||||
* SQLSTATE match here and retry uselessly, but there
|
||||
@ -2628,9 +2628,9 @@ internal_ping(PGconn *conn)
|
||||
|
||||
/*
|
||||
* If we failed to get any ERROR response from the postmaster, report
|
||||
* PQPING_NO_RESPONSE. This result could be somewhat misleading for a
|
||||
* PQPING_NO_RESPONSE. This result could be somewhat misleading for a
|
||||
* pre-7.4 server, since it won't send back a SQLSTATE, but those are long
|
||||
* out of support. Another corner case where the server could return a
|
||||
* out of support. Another corner case where the server could return a
|
||||
* failure without a SQLSTATE is fork failure, but NO_RESPONSE isn't
|
||||
* totally unreasonable for that anyway. We expect that every other
|
||||
* failure case in a modern server will produce a report with a SQLSTATE.
|
||||
@ -2849,7 +2849,7 @@ freePGconn(PGconn *conn)
|
||||
* - properly close a connection to the backend
|
||||
*
|
||||
* This should reset or release all transient state, but NOT the connection
|
||||
* parameters. On exit, the PGconn should be in condition to start a fresh
|
||||
* parameters. On exit, the PGconn should be in condition to start a fresh
|
||||
* connection with the same parameters (see PQreset()).
|
||||
*/
|
||||
static void
|
||||
@ -2985,7 +2985,7 @@ PQreset(PGconn *conn)
|
||||
if (connectDBStart(conn) && connectDBComplete(conn))
|
||||
{
|
||||
/*
|
||||
* Notify event procs of successful reset. We treat an event proc
|
||||
* Notify event procs of successful reset. We treat an event proc
|
||||
* failure as disabling the connection ... good idea?
|
||||
*/
|
||||
int i;
|
||||
@ -3045,7 +3045,7 @@ PQresetPoll(PGconn *conn)
|
||||
if (status == PGRES_POLLING_OK)
|
||||
{
|
||||
/*
|
||||
* Notify event procs of successful reset. We treat an event proc
|
||||
* Notify event procs of successful reset. We treat an event proc
|
||||
* failure as disabling the connection ... good idea?
|
||||
*/
|
||||
int i;
|
||||
@ -3234,7 +3234,7 @@ cancel_errReturn:
|
||||
* Returns TRUE if able to send the cancel request, FALSE if not.
|
||||
*
|
||||
* On failure, an error message is stored in *errbuf, which must be of size
|
||||
* errbufsize (recommended size is 256 bytes). *errbuf is not changed on
|
||||
* errbufsize (recommended size is 256 bytes). *errbuf is not changed on
|
||||
* success return.
|
||||
*/
|
||||
int
|
||||
@ -4011,7 +4011,7 @@ parseServiceFile(const char *serviceFile,
|
||||
* PQconninfoParse
|
||||
*
|
||||
* Parse a string like PQconnectdb() would do and return the
|
||||
* resulting connection options array. NULL is returned on failure.
|
||||
* resulting connection options array. NULL is returned on failure.
|
||||
* The result contains only options specified directly in the string,
|
||||
* not any possible default values.
|
||||
*
|
||||
|
||||
Reference in New Issue
Block a user