Tom Lane writes: > > Also, is the new relfilenode somehow guaranteed to > > not be assigned to another relation (pg_class tuple, I think)? > > I've been wondering about that myself. We might have to add a unique > index on pg_class.relfilenode to ensure this; otherwise, after OID > wraparound there would be no guarantees.
I've never been happy with the current setup. It's much too tempting to think file name = OID, both in the backend code and by external onlookers, especially since it's currently rare/impossible(?) for them to be different. It would be a lot clearer if relfilenode were replaced by an integer version, starting at 0, and the heap files were named "OID_VERSION". (In related news, how about filling up the oid/relfilenode numbers with zeros on the left, so a directory listing would reflect the numerical order?) -- Peter Eisentraut [EMAIL PROTECTED] ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org
