Horton
Menu

Re: DELETE vs TRUNCATE explanation

Mark Thornton <mthornton@optrak.com>

View thread
From: Mark Thornton <mthornton@optrak.com>
To: pgsql-performance@postgresql.org, cjames@emolecules.com
Date: 2012-07-11T21:32:33Z
Lists: pgsql-hackers, pgsql-performance 
On 11/07/12 21:18, Craig James wrote:
>
> It strikes me as a contrived case rather than a use case.  What sort 
> of app repeatedly fills and truncates a small table thousands of times 
> ... other than a test app to see whether you can do it or not?
If I have a lot of data which updates/inserts an existing table but I 
don't know if a given record will be an update or an insert, then I 
write all the 'new' data to a temporary table and then use sql 
statements to achieve the updates and inserts on the existing table.

Is there a better way of doing this in standard SQL?

Mark

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.