mirror of
https://github.com/postgres/postgres.git
synced 2025-09-02 04:21:28 +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:
@@ -1140,7 +1140,7 @@ selectDumpableTable(TableInfo *tbinfo)
|
||||
* Mark a type as to be dumped or not
|
||||
*
|
||||
* If it's a table's rowtype or an autogenerated array type, we also apply a
|
||||
* special type code to facilitate sorting into the desired order. (We don't
|
||||
* special type code to facilitate sorting into the desired order. (We don't
|
||||
* want to consider those to be ordinary types because that would bring tables
|
||||
* up into the datatype part of the dump order.) We still set the object's
|
||||
* dump flag; that's not going to cause the dummy type to be dumped, but we
|
||||
@@ -1511,7 +1511,7 @@ dumpTableData_insert(Archive *fout, void *dcontext)
|
||||
/*
|
||||
* These types are printed without quotes unless
|
||||
* they contain values that aren't accepted by the
|
||||
* scanner unquoted (e.g., 'NaN'). Note that
|
||||
* scanner unquoted (e.g., 'NaN'). Note that
|
||||
* strtod() and friends might accept NaN, so we
|
||||
* can't use that to test.
|
||||
*
|
||||
@@ -1745,7 +1745,7 @@ getTableDataFKConstraints(void)
|
||||
/*
|
||||
* guessConstraintInheritance:
|
||||
* In pre-8.4 databases, we can't tell for certain which constraints
|
||||
* are inherited. We assume a CHECK constraint is inherited if its name
|
||||
* are inherited. We assume a CHECK constraint is inherited if its name
|
||||
* matches the name of any constraint in the parent. Originally this code
|
||||
* tried to compare the expression texts, but that can fail for various
|
||||
* reasons --- for example, if the parent and child tables are in different
|
||||
@@ -2700,7 +2700,7 @@ getNamespaces(Archive *fout, int *numNamespaces)
|
||||
* getNamespaces
|
||||
*
|
||||
* NB: for pre-7.3 source database, we use object OID to guess whether it's
|
||||
* a system object or not. In 7.3 and later there is no guessing, and we
|
||||
* a system object or not. In 7.3 and later there is no guessing, and we
|
||||
* don't use objoid at all.
|
||||
*/
|
||||
static NamespaceInfo *
|
||||
@@ -2859,7 +2859,7 @@ getTypes(Archive *fout, int *numTypes)
|
||||
* auto-generated array type by checking the element type's typarray.
|
||||
* (Before that the test is capable of generating false positives.) We
|
||||
* still check for name beginning with '_', though, so as to avoid the
|
||||
* cost of the subselect probe for all standard types. This would have to
|
||||
* cost of the subselect probe for all standard types. This would have to
|
||||
* be revisited if the backend ever allows renaming of array types.
|
||||
*/
|
||||
|
||||
@@ -3004,8 +3004,8 @@ getTypes(Archive *fout, int *numTypes)
|
||||
|
||||
/*
|
||||
* If it's a base type, make a DumpableObject representing a shell
|
||||
* definition of the type. We will need to dump that ahead of the I/O
|
||||
* functions for the type. Similarly, range types need a shell
|
||||
* definition of the type. We will need to dump that ahead of the I/O
|
||||
* functions for the type. Similarly, range types need a shell
|
||||
* definition in case they have a canonicalize function.
|
||||
*
|
||||
* Note: the shell type doesn't have a catId. You might think it
|
||||
@@ -3733,7 +3733,7 @@ getFuncs(Archive *fout, int *numFuncs)
|
||||
* Find all user-defined functions. Normally we can exclude functions in
|
||||
* pg_catalog, which is worth doing since there are several thousand of
|
||||
* 'em. However, there are some extensions that create functions in
|
||||
* pg_catalog. In normal dumps we can still ignore those --- but in
|
||||
* pg_catalog. In normal dumps we can still ignore those --- but in
|
||||
* binary-upgrade mode, we must dump the member objects of the extension,
|
||||
* so be sure to fetch any such functions.
|
||||
*
|
||||
@@ -4727,7 +4727,7 @@ getIndexes(Archive *fout, TableInfo tblinfo[], int numTables)
|
||||
/*
|
||||
* In pre-7.4 releases, indkeys may contain more entries than
|
||||
* indnkeys says (since indnkeys will be 1 for a functional
|
||||
* index). We don't actually care about this case since we don't
|
||||
* index). We don't actually care about this case since we don't
|
||||
* examine indkeys except for indexes associated with PRIMARY and
|
||||
* UNIQUE constraints, which are never functional indexes. But we
|
||||
* have to allocate enough space to keep parseOidArray from
|
||||
@@ -4974,7 +4974,7 @@ getDomainConstraints(Archive *fout, TypeInfo *tyinfo)
|
||||
|
||||
/*
|
||||
* Make the domain depend on the constraint, ensuring it won't be
|
||||
* output till any constraint dependencies are OK. If the constraint
|
||||
* output till any constraint dependencies are OK. If the constraint
|
||||
* has not been validated, it's going to be dumped after the domain
|
||||
* anyway, so this doesn't matter.
|
||||
*/
|
||||
@@ -5725,7 +5725,7 @@ getTableAttrs(Archive *fout, TableInfo *tblinfo, int numTables)
|
||||
else if (fout->remoteVersion >= 90100)
|
||||
{
|
||||
/*
|
||||
* attcollation is new in 9.1. Since we only want to dump COLLATE
|
||||
* attcollation is new in 9.1. Since we only want to dump COLLATE
|
||||
* clauses for attributes whose collation is different from their
|
||||
* type's default, we use a CASE here to suppress uninteresting
|
||||
* attcollations cheaply.
|
||||
@@ -5980,7 +5980,7 @@ getTableAttrs(Archive *fout, TableInfo *tblinfo, int numTables)
|
||||
|
||||
/*
|
||||
* Defaults on a VIEW must always be dumped as separate ALTER
|
||||
* TABLE commands. Defaults on regular tables are dumped as
|
||||
* TABLE commands. Defaults on regular tables are dumped as
|
||||
* part of the CREATE TABLE if possible, which it won't be if
|
||||
* the column is not going to be emitted explicitly.
|
||||
*/
|
||||
@@ -6177,7 +6177,7 @@ getTableAttrs(Archive *fout, TableInfo *tblinfo, int numTables)
|
||||
|
||||
/*
|
||||
* If the constraint is inherited, this will be detected later
|
||||
* (in pre-8.4 databases). We also detect later if the
|
||||
* (in pre-8.4 databases). We also detect later if the
|
||||
* constraint must be split out from the table definition.
|
||||
*/
|
||||
}
|
||||
@@ -7016,7 +7016,7 @@ findComments(Archive *fout, Oid classoid, Oid objoid,
|
||||
|
||||
/*
|
||||
* Pre-7.2, pg_description does not contain classoid, so collectComments
|
||||
* just stores a zero. If there's a collision on object OID, well, you
|
||||
* just stores a zero. If there's a collision on object OID, well, you
|
||||
* get duplicate comments.
|
||||
*/
|
||||
if (fout->remoteVersion < 70200)
|
||||
@@ -7406,7 +7406,7 @@ dumpExtension(Archive *fout, ExtensionInfo *extinfo)
|
||||
|
||||
/*
|
||||
* Note that we're pushing extconfig (an OID array) back into
|
||||
* pg_extension exactly as-is. This is OK because pg_class OIDs are
|
||||
* pg_extension exactly as-is. This is OK because pg_class OIDs are
|
||||
* preserved in binary upgrade.
|
||||
*/
|
||||
if (strlen(extinfo->extconfig) > 2)
|
||||
@@ -8337,7 +8337,7 @@ dumpCompositeType(Archive *fout, TypeInfo *tyinfo)
|
||||
if (fout->remoteVersion >= 90100)
|
||||
{
|
||||
/*
|
||||
* attcollation is new in 9.1. Since we only want to dump COLLATE
|
||||
* attcollation is new in 9.1. Since we only want to dump COLLATE
|
||||
* clauses for attributes whose collation is different from their
|
||||
* type's default, we use a CASE here to suppress uninteresting
|
||||
* attcollations cheaply. atttypid will be 0 for dropped columns;
|
||||
@@ -8653,7 +8653,7 @@ dumpShellType(Archive *fout, ShellTypeInfo *stinfo)
|
||||
|
||||
/*
|
||||
* Note the lack of a DROP command for the shell type; any required DROP
|
||||
* is driven off the base type entry, instead. This interacts with
|
||||
* is driven off the base type entry, instead. This interacts with
|
||||
* _printTocEntry()'s use of the presence of a DROP command to decide
|
||||
* whether an entry needs an ALTER OWNER command. We don't want to alter
|
||||
* the shell type's owner immediately on creation; that should happen only
|
||||
@@ -8690,7 +8690,7 @@ dumpShellType(Archive *fout, ShellTypeInfo *stinfo)
|
||||
*
|
||||
* For some backwards compatibility with the older behavior, we forcibly
|
||||
* dump a PL if its handler function (and validator if any) are in a
|
||||
* dumpable namespace. That case is not checked here.
|
||||
* dumpable namespace. That case is not checked here.
|
||||
*
|
||||
* Also, if the PL belongs to an extension, we do not use this heuristic.
|
||||
* That case isn't checked here either.
|
||||
@@ -9376,7 +9376,7 @@ dumpFunc(Archive *fout, FuncInfo *finfo)
|
||||
|
||||
/*
|
||||
* COST and ROWS are emitted only if present and not default, so as not to
|
||||
* break backwards-compatibility of the dump without need. Keep this code
|
||||
* break backwards-compatibility of the dump without need. Keep this code
|
||||
* in sync with the defaults in functioncmds.c.
|
||||
*/
|
||||
if (strcmp(procost, "0") != 0)
|
||||
@@ -10152,7 +10152,7 @@ dumpOpclass(Archive *fout, OpclassInfo *opcinfo)
|
||||
* XXX RECHECK is gone as of 8.4, but we'll still print it if dumping an
|
||||
* older server's opclass in which it is used. This is to avoid
|
||||
* hard-to-detect breakage if a newer pg_dump is used to dump from an
|
||||
* older server and then reload into that old version. This can go away
|
||||
* older server and then reload into that old version. This can go away
|
||||
* once 8.3 is so old as to not be of interest to anyone.
|
||||
*/
|
||||
resetPQExpBuffer(query);
|
||||
@@ -10430,7 +10430,7 @@ dumpOpfamily(Archive *fout, OpfamilyInfo *opfinfo)
|
||||
* XXX RECHECK is gone as of 8.4, but we'll still print it if dumping an
|
||||
* older server's opclass in which it is used. This is to avoid
|
||||
* hard-to-detect breakage if a newer pg_dump is used to dump from an
|
||||
* older server and then reload into that old version. This can go away
|
||||
* older server and then reload into that old version. This can go away
|
||||
* once 8.3 is so old as to not be of interest to anyone.
|
||||
*/
|
||||
if (fout->remoteVersion >= 90100)
|
||||
@@ -11690,7 +11690,7 @@ dumpUserMappings(Archive *fout,
|
||||
* to fail if run by a non-superuser. Note that the view will show
|
||||
* umoptions as null if the user hasn't got privileges for the associated
|
||||
* server; this means that pg_dump will dump such a mapping, but with no
|
||||
* OPTIONS clause. A possible alternative is to skip such mappings
|
||||
* OPTIONS clause. A possible alternative is to skip such mappings
|
||||
* altogether, but it's not clear that that's an improvement.
|
||||
*/
|
||||
selectSourceSchema(fout, "pg_catalog");
|
||||
@@ -11831,7 +11831,7 @@ dumpDefaultACL(Archive *fout, DefaultACLInfo *daclinfo)
|
||||
* 'type' must be one of
|
||||
* TABLE, SEQUENCE, FUNCTION, LANGUAGE, SCHEMA, DATABASE, TABLESPACE,
|
||||
* FOREIGN DATA WRAPPER, SERVER, or LARGE OBJECT.
|
||||
* 'name' is the formatted name of the object. Must be quoted etc. already.
|
||||
* 'name' is the formatted name of the object. Must be quoted etc. already.
|
||||
* 'subname' is the formatted name of the sub-object, if any. Must be quoted.
|
||||
* 'tag' is the tag for the archive entry (typ. unquoted name of object).
|
||||
* 'nspname' is the namespace the object is in (NULL if none).
|
||||
@@ -12202,7 +12202,7 @@ dumpTable(Archive *fout, TableInfo *tbinfo)
|
||||
tbinfo->relacl);
|
||||
|
||||
/*
|
||||
* Handle column ACLs, if any. Note: we pull these with a separate
|
||||
* Handle column ACLs, if any. Note: we pull these with a separate
|
||||
* query rather than trying to fetch them during getTableAttrs, so
|
||||
* that we won't miss ACLs on system columns.
|
||||
*/
|
||||
@@ -12587,7 +12587,7 @@ dumpTableSchema(Archive *fout, TableInfo *tbinfo)
|
||||
* physical column order, including dropped columns, as in the
|
||||
* original. Therefore, we create dropped columns above and drop them
|
||||
* here, also updating their attlen/attalign values so that the
|
||||
* dropped column can be skipped properly. (We do not bother with
|
||||
* dropped column can be skipped properly. (We do not bother with
|
||||
* restoring the original attbyval setting.) Also, inheritance
|
||||
* relationships are set up by doing ALTER INHERIT rather than using
|
||||
* an INHERITS clause --- the latter would possibly mess up the column
|
||||
@@ -12959,7 +12959,7 @@ dumpIndex(Archive *fout, IndxInfo *indxinfo)
|
||||
|
||||
/*
|
||||
* If there's an associated constraint, don't dump the index per se, but
|
||||
* do dump any comment for it. (This is safe because dependency ordering
|
||||
* do dump any comment for it. (This is safe because dependency ordering
|
||||
* will have ensured the constraint is emitted first.) Note that the
|
||||
* emitted comment has to be shown as depending on the constraint, not
|
||||
* the index, in such cases.
|
||||
@@ -13299,7 +13299,7 @@ findLastBuiltinOid_V71(Archive *fout, const char *dbname)
|
||||
* find the last built in oid
|
||||
*
|
||||
* For 7.0, we do this by assuming that the last thing that initdb does is to
|
||||
* create the pg_indexes view. This sucks in general, but seeing that 7.0.x
|
||||
* create the pg_indexes view. This sucks in general, but seeing that 7.0.x
|
||||
* initdb won't be changing anymore, it'll do.
|
||||
*/
|
||||
static Oid
|
||||
@@ -14087,7 +14087,7 @@ getExtensionMembership(Archive *fout, ExtensionInfo extinfo[],
|
||||
{
|
||||
/*
|
||||
* Note: config tables are dumped without OIDs regardless of
|
||||
* the --oids setting. This is because row filtering
|
||||
* the --oids setting. This is because row filtering
|
||||
* conditions aren't compatible with dumping OIDs.
|
||||
*/
|
||||
makeTableDataInfo(configtbl, false);
|
||||
@@ -14208,7 +14208,7 @@ getDependencies(Archive *fout)
|
||||
|
||||
/*
|
||||
* Ordinarily, table rowtypes have implicit dependencies on their
|
||||
* tables. However, for a composite type the implicit dependency goes
|
||||
* tables. However, for a composite type the implicit dependency goes
|
||||
* the other way in pg_depend; which is the right thing for DROP but
|
||||
* it doesn't produce the dependency ordering we need. So in that one
|
||||
* case, we reverse the direction of the dependency.
|
||||
|
Reference in New Issue
Block a user