Tom Lane wrote:
Alvaro Herrera <[EMAIL PROTECTED]> writes:
On Tue, Jul 19, 2005 at 10:44:35PM -0400, Tom Lane wrote:
If it's a matter of whether VACUUM removes rows or not, that's expected:
open-transaction bookkeeping is done across the whole cluster. (This is
not something simple to change, since we may have to consider
transaction IDs in shared catalogs.)
I wonder if this restriction could be lifted if we tracked last-vacuum-
Xid per relation?
No, that's unrelated. What is of concern is the open-transaction
horizon.
From a Slony-I users standpoint - the idle transactions cause
pg_listener bloat, which can impact replication performance on busy sites.
--
Brad Nicholson 416-673-4106
Database Administrator, Afilias Canada Corp.
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
