| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Artiom Makarov <artiom(dot)makarov(at)gmail(dot)com> |
| 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 12:09:22 |
| Message-ID: | 201004051209.o35C9MB10324@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Artiom Makarov wrote:
> 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?
I have it on my personal TODO and will try to get it on the official
TODO soon.
> I see a workaround: switch off "on commit delete rows" on temp tables
> and use txid_current() to control transaction visibility.
OK.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Kindernay | 2010-04-05 14:28:35 | Huge table searching optimization |
| Previous Message | Artiom Makarov | 2010-04-05 07:56:54 | Re: temp table "on commit delete rows": transaction overhead |