| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Mladen Gogala <mladen(dot)gogala(at)vmsinfo(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Postgres insert performance and storage requirement compared to Oracle |
| Date: | 2010-10-26 22:50:37 |
| Message-ID: | AANLkTimf9Nj8A+Spiu9q3suvZ+h71CHXRFTXFo_5aBYj@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
On Tue, Oct 26, 2010 at 5:54 PM, Mladen Gogala
<mladen(dot)gogala(at)vmsinfo(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2010-10-26 23:16:53 | Re: Postgres insert performance and storage requirement compared to Oracle |
| Previous Message | Merlin Moncure | 2010-10-26 22:14:15 | Re: Postgres insert performance and storage requirement compared to Oracle |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-10-26 22:51:31 | Re: Select count(*), the sequel |
| Previous Message | Robert Haas | 2010-10-26 22:45:30 | Re: Select count(*), the sequel |