mirror of
https://github.com/postgres/postgres.git
synced 2025-11-22 12:22:45 +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:
@@ -229,7 +229,7 @@ ProcedureCreate(const char *procedureName,
|
||||
|
||||
/*
|
||||
* Do not allow polymorphic return type unless at least one input argument
|
||||
* is polymorphic. ANYRANGE return type is even stricter: must have an
|
||||
* is polymorphic. ANYRANGE return type is even stricter: must have an
|
||||
* ANYRANGE input (since we can't deduce the specific range type from
|
||||
* ANYELEMENT). Also, do not allow return type INTERNAL unless at least
|
||||
* one input argument is INTERNAL.
|
||||
@@ -676,7 +676,7 @@ ProcedureCreate(const char *procedureName,
|
||||
|
||||
/*
|
||||
* Set per-function configuration parameters so that the validation is
|
||||
* done with the environment the function expects. However, if
|
||||
* done with the environment the function expects. However, if
|
||||
* check_function_bodies is off, we don't do this, because that would
|
||||
* create dump ordering hazards that pg_dump doesn't know how to deal
|
||||
* with. (For example, a SET clause might refer to a not-yet-created
|
||||
@@ -948,7 +948,7 @@ sql_function_parse_error_callback(void *arg)
|
||||
|
||||
/*
|
||||
* Adjust a syntax error occurring inside the function body of a CREATE
|
||||
* FUNCTION or DO command. This can be used by any function validator or
|
||||
* FUNCTION or DO command. This can be used by any function validator or
|
||||
* anonymous-block handler, not only for SQL-language functions.
|
||||
* It is assumed that the syntax error position is initially relative to the
|
||||
* function body string (as passed in). If possible, we adjust the position
|
||||
@@ -1081,7 +1081,7 @@ match_prosrc_to_literal(const char *prosrc, const char *literal,
|
||||
|
||||
/*
|
||||
* This implementation handles backslashes and doubled quotes in the
|
||||
* string literal. It does not handle the SQL syntax for literals
|
||||
* string literal. It does not handle the SQL syntax for literals
|
||||
* continued across line boundaries.
|
||||
*
|
||||
* We do the comparison a character at a time, not a byte at a time, so
|
||||
|
||||
Reference in New Issue
Block a user