BUG #2394: Multiple TRUNCATE within transaction - Mailing list pgsql-bugs

From Alexander Kirpa
Subject BUG #2394: Multiple TRUNCATE within transaction
Date
Msg-id 200604140132.k3E1WGZs056119@wwwmaster.postgresql.org
Whole thread Raw
Responses Re: BUG #2394: Multiple TRUNCATE within transaction  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
The following bug has been logged online:

Bug reference:      2394
Logged by:          Alexander Kirpa
Email address:      postgres@bilteks.com
PostgreSQL version: 8.1.3
Operating system:   FreeBSD 6.0
Description:        Multiple TRUNCATE within transaction
Details:

Within one transaction each 'TRUNCATE TABLE' - "generate" as minimum one
file: 1 for table plus one on each index.

In case of many truncate (10-100 thousands or more) within one transaction,
postgres receive serious performance problem for current operation (create
and delete 100K files in not to easy task for filesystem) and, in future,
some system wide (postgres) performance lost as result of big size (1-2MB in
my case) of database directory.

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.

Best regards,
 Alexander Kirpa

pgsql-bugs by date:

Previous
From: "Raphael Jacquot"
Date:
Subject: BUG #2392: Feature request : point_ops
Next
From: "wangshj"
Date:
Subject: BUG #2395: Can't get right type oid by PQftype.