Re: Postgres insert performance and storage requirement compared to Oracle - Mailing list pgsql-performance

From Robert Haas
Subject Re: Postgres insert performance and storage requirement compared to Oracle
Date
Msg-id AANLkTimf9Nj8A+Spiu9q3suvZ+h71CHXRFTXFo_5aBYj@mail.gmail.com
Whole thread Raw
In response to Re: Postgres insert performance and storage requirement compared to Oracle  (Mladen Gogala <mladen.gogala@vmsinfo.com>)
Responses Re: Postgres insert performance and storage requirement compared to Oracle  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-performance
On Tue, Oct 26, 2010 at 5:54 PM, Mladen Gogala
<mladen.gogala@vmsinfo.com> wrote:
> The table is created with "on commit obliterate rows" option which means
> that there is no need to do "truncate". The "truncate" command is a heavy
> artillery. Truncating a temporary table is like shooting ducks in a duck
> pond, with a howitzer.

This is just not true.  ON COMMIT DELETE ROWS simply arranges for a
TRUNCATE to happen immediately before each commit.  See
PreCommit_on_commit_actions() in tablecmds.c.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-performance by date:

Previous
From: Robert Haas
Date:
Subject: Re: Select count(*), the sequel
Next
From: Tom Lane
Date:
Subject: Re: Select count(*), the sequel