From: Tom Lane <tgl@sss.pgh.pa.us>
To: Matteo Sgalaberni <sgala@sgala.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: database bloat, non removovable rows, slow query etc... [RESOLVED]
Date: Sat, 02 Sep 2006 10:21:23 -0400
Message-ID: <2191.1157206883@sss.pgh.pa.us> (raw)
In-Reply-To: <20060902083725.GB2266@sgala.com>
References: <20060901123915.GT2266@sgala.com>
<4027.1157121810@sss.pgh.pa.us>
<20060901172829.GX2266@sgala.com>
<12756.1157132120@sss.pgh.pa.us>
<20060902083725.GB2266@sgala.com>
Matteo Sgalaberni <sgala@sgala.com> writes:
> Good to know this...but why this behaviour? it'is lovely...:)
Open transactions are tracked across the whole cluster. This is
necessary when vacuuming shared catalogs. In principle we could
track per-database xmin values as well, but the distributed overhead
that'd be added to *every* GetSnapshotData call is a bit worrisome.
regards, tom lane
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: tgl@sss.pgh.pa.us, sgala@sgala.com
Subject: Re: database bloat, non removovable rows, slow query etc... [RESOLVED]
In-Reply-To: <2191.1157206883@sss.pgh.pa.us>
* 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