Horton
Menu

Re: DELETE vs TRUNCATE explanation

Craig Ringer <ringerc@ringerc.id.au>

View thread
From: Craig Ringer <ringerc@ringerc.id.au>
To: Matthew Woodcraft <matthew@woodcraft.me.uk>
Cc: pgsql-performance@postgresql.org
Date: 2012-07-12T01:23:16Z
Lists: pgsql-hackers, pgsql-performance 
On 07/12/2012 02:10 AM, Matthew Woodcraft wrote:
> I think a documentation change would be worthwhile. At the moment the 
> TRUNCATE page says, with no caveats, that it is faster than 
> unqualified DELETE.

+1  to updating the docs to reflect the fact that TRUNCATE may have a 
higher fixed cost than DELETE FROM table; but also prevents bloat.

It's a weird little corner case, but with database-backed unit testing 
it's going to become a more significant one whether or not it feels like 
it makes any sense.

--
Craig Ringer

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Scan the buffer pool just once, not once per fork, during relation drop.