"Alexander Kirpa" <[EMAIL PROTECTED]> writes:
> In case of many truncate (10-100 thousands or more) within one transaction,
> postgres receive serious performance problem for current operation (create
Why in the world are you doing that, and why do you think we need to
optimize that case? We don'
The following bug has been logged online:
Bug reference: 2394
Logged by: Alexander Kirpa
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: FreeBSD 6.0
Description:Multiple TRUNCATE within transaction
Details:
Within one transaction each 'T
