From: Tom Lane <tgl@sss.pgh.pa.us>
To: Gregory Stark <gsstark@mit.edu>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Matteo Sgalaberni <sgala@sgala.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: database bloat, non removovable rows, slow query etc... [RESOLVED]
Date: Mon, 04 Sep 2006 23:17:06 -0400
Message-ID: <18082.1157426226@sss.pgh.pa.us> (raw)
In-Reply-To: <878xkz17fs.fsf@stark.xeocode.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>
<2191.1157206883@sss.pgh.pa.us>
<87ejur1drl.fsf@stark.xeocode.com>
<20060904224716.GB14107@alvh.no-ip.org>
<878xkz17fs.fsf@stark.xeocode.com>
Gregory Stark <gsstark@mit.edu> writes:
> I must be misunderstanding Tom's comment then.
> What I'm referring to is lazy_vacuum_rel() calls vacuum_set_xid_limits with
> the relisshared flag of the relation. vacuum_set_xid_limits passes that to
> GetOldestXmin as the allDbs parameter. GetOldestXmin ignores transactions not
> connected to the same database unless allDbs is true.
The problem is the indirect effect of other backends' xmin values,
which are computed across all live backends.
In the current structure, it's hard to see how to fix this except
by making each backend compute and advertise both a global and
database-local xmin. This seems a bit ugly. Also, someone asked
recently whether we could avoid counting prepared xacts when figuring
vacuum cutoffs, which seems a fair question --- but again, how to do
that without doubling the number of advertised xmin values yet again?
I'm starting to feel that we've reached the limits of this system of
accounting for live XIDs, but I have no idea what the next step might
look like...
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, gsstark@mit.edu, alvherre@commandprompt.com, sgala@sgala.com
Subject: Re: database bloat, non removovable rows, slow query etc... [RESOLVED]
In-Reply-To: <18082.1157426226@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