Re: Disk Performance Problem on Large DB
| От | Scott Marlowe |
|---|---|
| Тема | Re: Disk Performance Problem on Large DB |
| Дата | |
| Msg-id | AANLkTimVtt+XP9+-bLtLzg2WDz+BZrDjXMrpA7GTn3k+@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Disk Performance Problem on Large DB (Samuel Stearns <SStearns@internode.com.au>) |
| Ответы |
Re: Disk Performance Problem on Large DB
|
| Список | pgsql-admin |
On Thu, Nov 4, 2010 at 9:33 PM, Samuel Stearns <SStearns@internode.com.au> wrote: > TRUNCATE doesn't generate any rollback data, which makes it lightning fast. It just de-allocates the data pages used bythe 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.)
В списке pgsql-admin по дате отправления: