mirror of
https://github.com/postgres/postgres.git
synced 2025-07-17 06:41:09 +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:
@ -176,7 +176,7 @@ check_datestyle(char **newval, void **extra, GucSource source)
|
||||
}
|
||||
|
||||
/*
|
||||
* Prepare the canonical string to return. GUC wants it malloc'd.
|
||||
* Prepare the canonical string to return. GUC wants it malloc'd.
|
||||
*/
|
||||
result = (char *) malloc(32);
|
||||
if (!result)
|
||||
@ -274,7 +274,7 @@ check_timezone(char **newval, void **extra, GucSource source)
|
||||
if (pg_strncasecmp(*newval, "interval", 8) == 0)
|
||||
{
|
||||
/*
|
||||
* Support INTERVAL 'foo'. This is for SQL spec compliance, not
|
||||
* Support INTERVAL 'foo'. This is for SQL spec compliance, not
|
||||
* because it has any actual real-world usefulness.
|
||||
*/
|
||||
const char *valueptr = *newval;
|
||||
@ -298,7 +298,7 @@ check_timezone(char **newval, void **extra, GucSource source)
|
||||
|
||||
/*
|
||||
* Try to parse it. XXX an invalid interval format will result in
|
||||
* ereport(ERROR), which is not desirable for GUC. We did what we
|
||||
* ereport(ERROR), which is not desirable for GUC. We did what we
|
||||
* could to guard against this in flatten_set_variable_args, but a
|
||||
* string coming in from postgresql.conf might contain anything.
|
||||
*/
|
||||
@ -374,11 +374,11 @@ check_timezone(char **newval, void **extra, GucSource source)
|
||||
}
|
||||
|
||||
/*
|
||||
* Prepare the canonical string to return. GUC wants it malloc'd.
|
||||
* Prepare the canonical string to return. GUC wants it malloc'd.
|
||||
*
|
||||
* Note: the result string should be something that we'd accept as input.
|
||||
* We use the numeric format for interval cases, because it's simpler to
|
||||
* reload. In the named-timezone case, *newval is already OK and need not
|
||||
* reload. In the named-timezone case, *newval is already OK and need not
|
||||
* be changed; it might not have the canonical casing, but that's taken
|
||||
* care of by show_timezone.
|
||||
*/
|
||||
@ -534,7 +534,7 @@ show_log_timezone(void)
|
||||
* We allow idempotent changes (r/w -> r/w and r/o -> r/o) at any time, and
|
||||
* we also always allow changes from read-write to read-only. However,
|
||||
* read-only may be changed to read-write only when in a top-level transaction
|
||||
* that has not yet taken an initial snapshot. Can't do it in a hot standby
|
||||
* that has not yet taken an initial snapshot. Can't do it in a hot standby
|
||||
* slave, either.
|
||||
*
|
||||
* If we are not in a transaction at all, just allow the change; it means
|
||||
@ -695,7 +695,7 @@ check_transaction_deferrable(bool *newval, void **extra, GucSource source)
|
||||
*
|
||||
* We can't roll back the random sequence on error, and we don't want
|
||||
* config file reloads to affect it, so we only want interactive SET SEED
|
||||
* commands to set it. We use the "extra" storage to ensure that rollbacks
|
||||
* commands to set it. We use the "extra" storage to ensure that rollbacks
|
||||
* don't try to do the operation again.
|
||||
*/
|
||||
|
||||
@ -971,7 +971,7 @@ const char *
|
||||
show_role(void)
|
||||
{
|
||||
/*
|
||||
* Check whether SET ROLE is active; if not return "none". This is a
|
||||
* Check whether SET ROLE is active; if not return "none". This is a
|
||||
* kluge to deal with the fact that SET SESSION AUTHORIZATION logically
|
||||
* resets SET ROLE to NONE, but we cannot set the GUC role variable from
|
||||
* assign_session_authorization (because we haven't got enough info to
|
||||
|
Reference in New Issue
Block a user