From: Mario Weilguni <mweilguni@sime.com>
To: pgsql-performance@postgresql.org
Subject: Re: vacuum locking
Date: Thu, 23 Oct 2003 08:14:56 +0200
Message-ID: <200310230814.56738.mweilguni@sime.com> (raw)
In-Reply-To: <16279.4988.496000.539525@gargle.gargle.HOWL>
References: <16272.318.870000.93584@gargle.gargle.HOWL>
<x7d6cpcdsr.fsf@yertle.int.kciLink.com>
<16279.4988.496000.539525@gargle.gargle.HOWL>
Am Donnerstag, 23. Oktober 2003 01:32 schrieb Rob Nagler:
> The concept of vacuuming seems to be problematic. I'm not sure why
> the database simply can't garbage collect incrementally. AGC is very
> tricky, especially AGC that involves gigabytes of data on disk.
> Incremental garbage collection seems to be what other databases do,
> and it's been my experience that other databases don't have the type
> of unpredictable behavior I'm seeing with Postgres. I'd rather the
> database be a little bit slower on average than have to figure out the
> best time to inconvenience my users.
I think oracle does not do garbage collect, it overwrites the tuples directly
and stores the old tuples in undo buffers. Since most transactions are
commits, this is a big win.
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: mweilguni@sime.com
Subject: Re: vacuum locking
In-Reply-To: <200310230814.56738.mweilguni@sime.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