Re: temp table "on commit delete rows": transaction overhead

From: Artiom Makarov <artiom(dot)makarov(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-performance(at)postgresql(dot)org
Subject: Re: temp table "on commit delete rows": transaction overhead
Date: 2010-04-05 07:56:54
Message-ID: q2td448ea361004050056ifed022e3t3ca6e2cca7eaac61@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

2010/4/1 Bruce Momjian <bruce(at)momjian(dot)us>:

> I think one of the problems is that we do the truncate even if the table
> has not be touched by the query, which is poor behavior.

Thank you for the support.
Will be this problem registered?

PS
I see a workaround: switch off "on commit delete rows" on temp tables
and use txid_current() to control transaction visibility.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Bruce Momjian 2010-04-05 12:09:22 Re: temp table "on commit delete rows": transaction overhead
Previous Message Lew 2010-04-04 21:17:26 Re: Using high speed swap to improve performance?