Am Freitag, 18. Januar 2008 schrieb Dave Page: > It got figured out when someone who knew what they were looking for > peeked at the byte ordering in a file which for all we knew at the > time might have been damaged anyway What might be better is if we had an explicit endianness mark in pg_control rather than relying on users discovering endianness problems by seemingly corrupted version numbers. > For just about zero cost we could drop something like: > > -------- > Architecture: Darwin snake 8.11.1 Darwin Kernel Version 8.11.1: Wed > Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/RELEASE_I386 i386 i386 I think we should address the problem were it happens. Adding this output will increase the amount of information available for causing confusion, while it would probably still require expert knowledge to read an endianness issue out of that. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
