mirror of
https://github.com/postgres/postgres.git
synced 2025-06-14 18:42:34 +03:00
pgindent run for 9.4
This includes removing tabs after periods in C comments, which was applied to back branches, so this change should not effect backpatching.
This commit is contained in:
@ -94,7 +94,7 @@ static int check_field_number(const PGresult *res, int field_num);
|
||||
* doesn't tell us up front how many tuples will be returned.)
|
||||
* All other subsidiary storage for a PGresult is kept in PGresult_data blocks
|
||||
* of size PGRESULT_DATA_BLOCKSIZE. The overhead at the start of each block
|
||||
* is just a link to the next one, if any. Free-space management info is
|
||||
* is just a link to the next one, if any. Free-space management info is
|
||||
* kept in the owning PGresult.
|
||||
* A query returning a small amount of data will thus require three malloc
|
||||
* calls: one for the PGresult, one for the tuples pointer array, and one
|
||||
@ -113,7 +113,7 @@ static int check_field_number(const PGresult *res, int field_num);
|
||||
* blocks, instead of being crammed into a regular allocation block.
|
||||
* Requirements for correct function are:
|
||||
* PGRESULT_ALIGN_BOUNDARY must be a multiple of the alignment requirements
|
||||
* of all machine data types. (Currently this is set from configure
|
||||
* of all machine data types. (Currently this is set from configure
|
||||
* tests, so it should be OK automatically.)
|
||||
* PGRESULT_SEP_ALLOC_THRESHOLD + PGRESULT_BLOCK_OVERHEAD <=
|
||||
* PGRESULT_DATA_BLOCKSIZE
|
||||
@ -268,10 +268,10 @@ PQsetResultAttrs(PGresult *res, int numAttributes, PGresAttDesc *attDescs)
|
||||
* Returns a deep copy of the provided 'src' PGresult, which cannot be NULL.
|
||||
* The 'flags' argument controls which portions of the result will or will
|
||||
* NOT be copied. The created result is always put into the
|
||||
* PGRES_TUPLES_OK status. The source result error message is not copied,
|
||||
* PGRES_TUPLES_OK status. The source result error message is not copied,
|
||||
* although cmdStatus is.
|
||||
*
|
||||
* To set custom attributes, use PQsetResultAttrs. That function requires
|
||||
* To set custom attributes, use PQsetResultAttrs. That function requires
|
||||
* that there are no attrs contained in the result, so to use that
|
||||
* function you cannot use the PG_COPYRES_ATTRS or PG_COPYRES_TUPLES
|
||||
* options with this function.
|
||||
@ -299,7 +299,7 @@ PQcopyResult(const PGresult *src, int flags)
|
||||
if (!dest)
|
||||
return NULL;
|
||||
|
||||
/* Always copy these over. Is cmdStatus really useful here? */
|
||||
/* Always copy these over. Is cmdStatus really useful here? */
|
||||
dest->client_encoding = src->client_encoding;
|
||||
strcpy(dest->cmdStatus, src->cmdStatus);
|
||||
|
||||
@ -757,7 +757,7 @@ pqPrepareAsyncResult(PGconn *conn)
|
||||
PGresult *res;
|
||||
|
||||
/*
|
||||
* conn->result is the PGresult to return. If it is NULL (which probably
|
||||
* conn->result is the PGresult to return. If it is NULL (which probably
|
||||
* shouldn't happen) we assume there is an appropriate error message in
|
||||
* conn->errorMessage.
|
||||
*/
|
||||
@ -778,7 +778,7 @@ pqPrepareAsyncResult(PGconn *conn)
|
||||
/*
|
||||
* Replace conn->result with next_result, if any. In the normal case
|
||||
* there isn't a next result and we're just dropping ownership of the
|
||||
* current result. In single-row mode this restores the situation to what
|
||||
* current result. In single-row mode this restores the situation to what
|
||||
* it was before we created the current single-row result.
|
||||
*/
|
||||
conn->result = conn->next_result;
|
||||
@ -1569,7 +1569,7 @@ pqHandleSendFailure(PGconn *conn)
|
||||
/* loop until no more data readable */ ;
|
||||
|
||||
/*
|
||||
* Parse any available input messages. Since we are in PGASYNC_IDLE
|
||||
* Parse any available input messages. Since we are in PGASYNC_IDLE
|
||||
* state, only NOTICE and NOTIFY messages will be eaten.
|
||||
*/
|
||||
parseInput(conn);
|
||||
@ -1789,7 +1789,7 @@ getCopyResult(PGconn *conn, ExecStatusType copytype)
|
||||
* If the server connection has been lost, don't pretend everything is
|
||||
* hunky-dory; instead return a PGRES_FATAL_ERROR result, and reset the
|
||||
* asyncStatus to idle (corresponding to what we'd do if we'd detected I/O
|
||||
* error in the earlier steps in PQgetResult). The text returned in the
|
||||
* error in the earlier steps in PQgetResult). The text returned in the
|
||||
* result is whatever is in conn->errorMessage; we hope that was filled
|
||||
* with something relevant when the lost connection was detected.
|
||||
*/
|
||||
@ -2031,7 +2031,7 @@ PQexecFinish(PGconn *conn)
|
||||
* If the query was not even sent, return NULL; conn->errorMessage is set to
|
||||
* a relevant message.
|
||||
* If the query was sent, a new PGresult is returned (which could indicate
|
||||
* either success or failure). On success, the PGresult contains status
|
||||
* either success or failure). On success, the PGresult contains status
|
||||
* PGRES_COMMAND_OK, and its parameter and column-heading fields describe
|
||||
* the statement's inputs and outputs respectively.
|
||||
* The user is responsible for freeing the PGresult via PQclear()
|
||||
@ -2374,7 +2374,7 @@ PQgetCopyData(PGconn *conn, char **buffer, int async)
|
||||
* PQgetline - gets a newline-terminated string from the backend.
|
||||
*
|
||||
* Chiefly here so that applications can use "COPY <rel> to stdout"
|
||||
* and read the output string. Returns a null-terminated string in s.
|
||||
* and read the output string. Returns a null-terminated string in s.
|
||||
*
|
||||
* XXX this routine is now deprecated, because it can't handle binary data.
|
||||
* If called during a COPY BINARY we return EOF.
|
||||
@ -2488,7 +2488,7 @@ PQputnbytes(PGconn *conn, const char *buffer, int nbytes)
|
||||
* the application must call this routine to finish the command protocol.
|
||||
*
|
||||
* When using protocol 3.0 this is deprecated; it's cleaner to use PQgetResult
|
||||
* to get the transfer status. Note however that when using 2.0 protocol,
|
||||
* to get the transfer status. Note however that when using 2.0 protocol,
|
||||
* recovering from a copy failure often requires a PQreset. PQendcopy will
|
||||
* take care of that, PQgetResult won't.
|
||||
*
|
||||
@ -2716,7 +2716,7 @@ PQfname(const PGresult *res, int field_num)
|
||||
* downcasing in the frontend might follow different locale rules than
|
||||
* downcasing in the backend...
|
||||
*
|
||||
* Returns -1 if no match. In the present backend it is also possible
|
||||
* Returns -1 if no match. In the present backend it is also possible
|
||||
* to have multiple matches, in which case the first one is found.
|
||||
*/
|
||||
int
|
||||
@ -3149,7 +3149,7 @@ PQfreemem(void *ptr)
|
||||
*
|
||||
* This function is here only for binary backward compatibility.
|
||||
* New code should use PQfreemem(). A macro will automatically map
|
||||
* calls to PQfreemem. It should be removed in the future. bjm 2003-03-24
|
||||
* calls to PQfreemem. It should be removed in the future. bjm 2003-03-24
|
||||
*/
|
||||
|
||||
#undef PQfreeNotify
|
||||
@ -3344,7 +3344,7 @@ PQescapeInternal(PGconn *conn, const char *str, size_t len, bool as_ident)
|
||||
/*
|
||||
* If we are escaping a literal that contains backslashes, we use the
|
||||
* escape string syntax so that the result is correct under either value
|
||||
* of standard_conforming_strings. We also emit a leading space in this
|
||||
* of standard_conforming_strings. We also emit a leading space in this
|
||||
* case, to guard against the possibility that the result might be
|
||||
* interpolated immediately following an identifier.
|
||||
*/
|
||||
|
Reference in New Issue
Block a user