From: Adriaan Joubert <a.joubert@albourne.com>
To: Ed Loehr <ELOEHR@austin.rr.com>
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Is it safe to INSERT/DELETE during VACUUM?
Date: Tue, 14 Dec 1999 08:45:03 +0200
Message-ID: <3855E76F.9F183684@albourne.com> (raw)
References: <14421.4341.805191.194488@ampato.aeccom.com>
<38553CEA.8CFFD543@austin.rr.com>
<38555166.32D789CA@austin.rr.com>
Ed Loehr wrote:
>
> Question: is it safe to insert/update/delete during VACUUM?
>
It is supposed to be (MVCC should take care of it), but in practice I've
got bad experiences with it. The system should at least have a very low
load. You can get dead-lock errors, as the tables being vacuumed are
locked for a long time and then inaccessible to other queries (that's
unavoidable, but still annoying). And a couple of times something went
wrong and I ended up with duplicate tuples in my tables -- really
duplicate, including the oid's. That required a table
dump/sort/uniq/load to fix :-(.
Adriaan
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-interfaces@postgresql.org
Cc: a.joubert@albourne.com, ELOEHR@austin.rr.com, pgsql-general@postgresql.org
Subject: Re: [GENERAL] Is it safe to INSERT/DELETE during VACUUM?
In-Reply-To: <3855E76F.9F183684@albourne.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