From: | Willem Leenen <willem_leenen(at)hotmail(dot)com> |
---|---|
To: | <mike(dot)blackwell(at)rrd(dot)com>, <klaussfreire(at)gmail(dot)com> |
Cc: | <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Savepoints in transactions for speed? |
Date: | 2012-11-28 15:23:21 |
Message-ID: | DUB104-W3775F9EFC7F49ED475B188F5D0@phx.gbl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Commitmarks are written to disk after each transaction. So transactionsize has impact on performance.
Date: Wed, 28 Nov 2012 09:18:20 -0600
Subject: Re: [PERFORM] Savepoints in transactions for speed?
From: mike(dot)blackwell(at)rrd(dot)com
To: klaussfreire(at)gmail(dot)com
CC: pgsql-performance(at)postgresql(dot)org
On Tue, Nov 27, 2012 at 7:16 PM, Claudio Freire <klaussfreire(at)gmail(dot)com> wrote:
Updates, are faster if batched, if your business logic allows it,
because it creates less bloat and creates more opportunities for with
HOT updates. I don't think it applies to inserts, though, and I
haven't heard it either.
Ah. That must have been what I'd half-remembered. Thanks for the clarification.
Mike
From | Date | Subject | |
---|---|---|---|
Next Message | Niels Kristian Schjødt | 2012-11-28 16:19:17 | Re: Optimize update query |
Previous Message | Mike Blackwell | 2012-11-28 15:18:20 | Re: Savepoints in transactions for speed? |