Tom Lane kirjoitti:
I'm also concerned about loss of debug traceability if these fields disappear entirely from disk --- it's been handy more than once to be able to tell where in a complex transaction something happened.
Sure. We'll just have to try to compensate that with debug messages etc., whatever scheme we choose.
Lastly, at least on machines with 8-byte MAXALIGN, removing four more bytes from heap headers would save nothing. So I'm not excited about going through enormous pushups to get rid of both fields, when a far simpler and better-performing mechanism suffices to remove one.
It would be a win on 32-bit architectures. And there has been discussion of storing at least some data types unaligned. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
