|
15 | 15 | *oids are the same between old and new clusters. This is important |
16 | 16 | *because toast oids are stored as toast pointers in user tables. |
17 | 17 | * |
18 | | - *FYI, while pg_class.oid and pg_class.relfilenode are initially the same |
19 | | - *in a cluster, but they can diverge due to CLUSTER, REINDEX, or VACUUM |
20 | | - *FULL. The new cluster will have matching pg_class.oid and |
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. 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. |
| 18 | + *While pg_class.oid and pg_class.relfilenode are initially the same |
| 19 | + *in a cluster, they can diverge due to CLUSTER, REINDEX, or VACUUM |
| 20 | + *FULL. In the new cluster, pg_class.oid and pg_class.relfilenode will |
| 21 | + *be the same and will match the old pg_class.oid value. Because of |
| 22 | + *this, old/new pg_class.relfilenode values will not match if CLUSTER, |
| 23 | + *REINDEX, or VACUUM FULL have been performed in the old cluster. |
25 | 24 | * |
26 | 25 | *We control all assignments of pg_type.oid because these oids are stored |
27 | 26 | *in user composite type values. |
|