Re: Disk Performance Problem on Large DB

Yep!

Coming from previous Oracle job into Postgres, discovering the transactable stuff, is indeed, pretty cool.

-----Original Message-----
From: Scott Marlowe [mailto:scott(dot)marlowe(at)gmail(dot)com]
Sent: Friday, 5 November 2010 2:12 PM
To: Samuel Stearns
Cc: Jonathan Hoover; pgsql-admin(at)postgresql(dot)org; Kenneth Marshall
Subject: Re: [ADMIN] Disk Performance Problem on Large DB

On Thu, Nov 4, 2010 at 9:33 PM, Samuel Stearns
<SStearns(at)internode(dot)com(dot)au> wrote:
> TRUNCATE doesn't generate any rollback data, which makes it lightning fast. It just de-allocates the data pages used by the table.

Also truncate, like nearly everything in pgsql, can be rolled back. I
still remember showing my oracle co-dbas in my last job freak out when
I showed them things like

begin;
update table yada...
truncate table;
rollback;

or
begin;
drop index xyz;
explain select ...
rollback;

transactable everything is pretty cool. (note database and tablespace
craete / drop are the only things that aren't transactable, which
makes some sense.)