Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > So, is this an option we want for configure? > > I think the case for it got a whole lot weaker in 8.3, with lazy > consumption of CIDs. If someone had tables big enough to make the > 32-bit-CID limit still be a problem despite that fix, I'd think they'd > not be very happy about adding another 4 bytes of tuple header overhead > (or more likely 8 bytes, on the kind of machine where this patch would > make some sense). I don't foresee many people paying that cost rather > than breaking up their transactions. > > My feeling is we should avoid the extra complexity, at least till such > time as we see whether there are still any real field complaints about > this with 8.3. > > In any case the patch is broken by --enable-float8-byval, and would > need some adjustments to play nice with that.
Agreed. Let's see if we get requests for it in >= 8.3 releases. -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-patches
