Re: Solving the OID-collision problem - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Solving the OID-collision problem
Date
Msg-id 15797.1123167321@sss.pgh.pa.us
Whole thread Raw
In response to Re: Solving the OID-collision problem  ("Mark Woodward" <pgsql@mohawksoft.com>)
Responses Re: Solving the OID-collision problem  ("Mark Woodward" <pgsql@mohawksoft.com>)
List pgsql-hackers
"Mark Woodward" <pgsql@mohawksoft.com> writes:
>> 2. Performance.  Doing this would require widening Datum to 64 bits,
>> which is a system-wide performance hit on 32-bit machines.

> Do you really think it would make a measurable difference, more so than
> your proposed solution? (I'm skeptical it would be measurable at all)

I'm too lazy to run an experiment, but I believe it would.  Datum is
involved in almost every function-call API in the backend.  In
particular this means that it would affect performance-critical code
paths.  Creation of tables and such isn't performance-critical in most
applications, so a few percent overhead there doesn't bother me.  A few
percent across the board is another story.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Mark Woodward"
Date:
Subject: Re: Solving the OID-collision problem
Next
From: "Mark Woodward"
Date:
Subject: Re: Solving the OID-collision problem