On Tue, Nov 01, 2005 at 04:54:11PM -0500, Tom Lane wrote: > It might be reasonable to restrict the range of NUMERIC to the point > that we could fit the weight/sign/dscale into 2 bytes instead of 4, > thereby saving 2 bytes per NUMERIC. I'm not excited about the other > aspects of this, though.
FWIW, most databases I've used limit NUMERIC to 38 digits, presumably to fit length info into 1 or 2 bytes. So there's something to be said for a small numeric type that has less overhead and a large numeric (what we have today). -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
