Commit2f657e4

committed

More pg_upgrade relfilenode C comments added.

1 parent3095643 commit2f657e4Copy full SHA for 2f657e4

File tree

-1

lines changed

-1

lines changed

Lines changed: 6 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -132,7 +132,13 @@ create_rel_filename_map(const char old_data, const char new_data,`
`132`	`132`	`new_cluster.tablespace_suffix,new_db->db_oid);`
`133`	`133`	`}`
`134`	`134`
	`135`	`+/*`
	`136`	`+ *old_relfilenode might differ from pg_class.oid (and hence`
	`137`	`+ *new_relfilenode) because of CLUSTER, REINDEX, or VACUUM FULL.`
	`138`	`+ */`
`135`	`139`	`map->old_relfilenode=old_rel->relfilenode;`
	`140`	`+`
	`141`	`+/* new_relfilenode will match old and new pg_class.oid */`
`136`	`142`	`map->new_relfilenode=new_rel->relfilenode;`
`137`	`143`
`138`	`144`	`/* used only for logging and error reporing, old/new are identical */`

Lines changed: 3 additions & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -19,7 +19,9 @@`
`19`	`19`	`*in a cluster, but they can diverge due to CLUSTER, REINDEX, or VACUUM`
`20`	`20`	`*FULL. The new cluster will have matching pg_class.oid and`
`21`	`21`	`*pg_class.relfilenode values and be based on the old oid value. This can`
`22`		`- *cause the old and new pg_class.relfilenode values to differ.`
	`22`	`+ *cause the old and new pg_class.relfilenode values to differ. In summary,`
	`23`	`+ *old and new pg_class.oid and new pg_class.relfilenode will have the`
	`24`	`+ *same value, and old pg_class.relfilenode might differ.`
`23`	`25`	`*`
`24`	`26`	`*We control all assignments of pg_type.oid because these oids are stored`
`25`	`27`	`*in user composite type values.`

Comments

(0)