| From: | Adriaan Joubert <a(dot)joubert(at)albourne(dot)com> |
|---|---|
| To: | Ed Loehr <ELOEHR(at)austin(dot)rr(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] Is it safe to INSERT/DELETE during VACUUM? |
| Date: | 1999-12-14 06:45:03 |
| Message-ID: | 3855E76F.9F183684@albourne.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-interfaces |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Elmar.Haneke | 1999-12-14 08:30:51 | Access rescrictions |
| Previous Message | Jared King | 1999-12-14 04:06:29 | (no subject) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Constantin Teodorescu | 1999-12-14 08:42:59 | Tcl 8.2 , multithreading and libpgtcl |
| Previous Message | Peter Eisentraut | 1999-12-13 23:28:28 | Re: [GENERAL] [GENERAL/INTERFACES] Dynamically detecting need to vacuum? |