"Alexander Kirpa" <postgres@bilteks.com> 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't have infinite manpower, so if you
want this case optimized you had better explain why it deserves
consideration ahead of the long list of other problems ...
> IMHO, need create new file only for first of truncate command. For 2, 3, ...
> 'truncate table' within one transaction need simple truncate self file(s),
> this also improve performance especially in case using of temporary tables
> by avoid write temporary date on disk.
This "simple" fix is pretty debatable anyway because of the existence
of intra-transaction MVCC rules.
regards, tom lane
