From: Veikko Mäkinen <veikko.makinen@ecom.fi>
To: pgsql-performance@postgresql.org
Subject: How does the transaction buffer work?
Date: Thu, 16 Jun 2005 22:28:30 +0300
Message-ID: <42B1D2DE.4020709@ecom.fi> (raw)
Hey,
How does Postgres (8.0.x) buffer changes to a database within a
transaction? I need to insert/update more than a thousand rows (mayde
even more than 10000 rows, ~100 bytes/row) in a table but the changes
must not be visible to other users/transactions before every row is
updated. One way of doing this that I thought of was start a
transaction, delete everything and then just dump new data in (copy
perhaps). The old data would be usable to other transactions until I
commit my insert. This would be the fastest way, but how much memory
would this use? Will this cause performance issues on a heavily loaded
server with too little memory even to begin with :)
-veikko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: veikko.makinen@ecom.fi
Subject: Re: How does the transaction buffer work?
In-Reply-To: <42B1D2DE.4020709@ecom.fi>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox