Re: Performance issue on temporary relations

>> It is unfair to add a performance penalty to everyone just because some
>> people write bad code. I concur that adding complexity to the system to
>> gracefully handle this corner-case doesn't seem justified. A use case
>> description, not mere existence, is needed to provide such justification.

> Yeah, the real sub-text here is "should we believe that this
> application is well designed?". It sounds like a fairly brute-force
> solution.

I agree the application is not well designed for PostgreSQL because it was migrated
from Oracle, and may not do such optimization. But back to this issue, even though
we only create 10 temporary relations, it will cause 10 truncates on every transaction.
Is that a good design?

Regards,
Jet

Halo Tech (www.halodbtech.com)
openHalo (www.openhalo.org)