From: Josh Berkus <josh@agliodbs.com>
To: Veikko Mäkinen <veikko.makinen@ecom.fi>
Cc: pgsql-performance@postgresql.org
Subject: Re: How does the transaction buffer work?
Date: Thu, 16 Jun 2005 14:53:36 -0700
Message-ID: <200506161453.37194.josh@agliodbs.com> (raw)
In-Reply-To: <42B1D2DE.4020709@ecom.fi>
References: <42B1D2DE.4020709@ecom.fi>
Veikko,
> 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?
Starting a transaction doesn't use any more memory than without one.
Unlike Some Other Databases, PostgreSQL's transactions occur in WAL and on
data pages, not in RAM.
> Will this cause performance issues on a heavily loaded
> server with too little memory even to begin with :)
Quite possibly, but the visibility issue won't be the problem.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, veikko.makinen@ecom.fi
Subject: Re: How does the transaction buffer work?
In-Reply-To: <200506161453.37194.josh@agliodbs.com>
* 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