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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Tom Lane wrote:
> Artiom Makarov <artiom.makarov@xxxxxxxxx> writes:
> > When temp tables with "on commit delete rows" exists, I can see a
> > strange delay at any “begin” and “commit”.
> 
> A delay at commit is hardly surprising, because each such temp table
> requires filesystem operations at commit (basically an "ftruncate").
> I don't recall any operations at transaction start for such tables,
> but there may be some.

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.

-- 
  Bruce Momjian  <bruce@xxxxxxxxxx>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

-- 
Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance

[Postgresql General]     [Postgresql PHP]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Yosemite]

  Powered by Linux