From: Rod Taylor <pg@rbt.ca>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org, Veikko Mäkinen <veikko.makinen@ecom.fi>
Subject: Re: How does the transaction buffer work?
Date: Fri, 17 Jun 2005 01:05:15 -0400
Message-ID: <1118984715.78366.240.camel@home> (raw)
In-Reply-To: <15555.1118981289@sss.pgh.pa.us>
References: <42B1D2DE.4020709@ecom.fi>
<15555.1118981289@sss.pgh.pa.us>
> Now of course this isn't Nirvana, you must pay somewhere ;-) and our
> weak spot is the need for VACUUM. But you have no need to fear large
> individual transactions.
No need to fear long running transactions other than their ability to
stop VACUUM from doing what it's supposed to be doing, thus possibly
impacting performance.
--
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: pg@rbt.ca, tgl@sss.pgh.pa.us, veikko.makinen@ecom.fi
Subject: Re: How does the transaction buffer work?
In-Reply-To: <1118984715.78366.240.camel@home>
* 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