On Fri, 2007-11-09 at 09:06 -0800, Kasia Tuszynska wrote:
> Hello Everybody,
> I am trying to establish what does Autovaccum actually do, as it is causing data load failures?
Autovacuum is a daemon that triggers vacuums when enough dead tuples are
generated in a table. The idea is that if it set up properly, the
database can automatically vacuum the tables when they need to get
vacuumed as opposed to the administrator having to do it manually.
There is still some tuning involved, and it's not perfect, but that's
another story.
There is no difference in the work that is actually done between a
vacuum triggered by autovacuum and one triggered manually.
> I ask because I am running into a weird scenario with large dataloads and the autovacuum process.
> My setup:
> Windows 2003 server, sp2
> PostgreSQL 8.2.4 installed from the gui (autovacuum on in postmaster.conf by default, no changes to postmaster.conf
atall)
> Type of data loaded: large spatial (non postgis) -> lots of blob data(4 gigs)
>
> This is my scenario:
> I am loading various sets of data, on several ones (that happen to be very large)it seems like the autovacuum
thresholdis triggered and on these select few datasets it crashes the postmaster:
> With code -1073741819, which I looked up to mean an access violation to an address space, it was apparently bugged:
Can you provide a bit more info on this data load procedure? Are you deleting from a table then loading the data?
Are you loading into a table that already has data that is being changed? How are you loading it? Is it all in
one transaction?
A data load itself should not trigger a vacuum. Dead tuples are created by updating or deleting tuples, not by
inserting
them. You will need to analyze the table afterwards, it's possibe that autovac is triggering that analyze.
> BUG #3427: Autovacuum crashed server
>
> http://archives.postgresql.org/pgsql-bugs/2007-07/msg00016.php
>
> The bug does not explain what is actually happening, what is autovacuum doing to get an access violation, why would
ithappen on very specific data everytime ?
I really don't know anything about Windows, but on UNIX, if a process
dies a hard enough death, it can corrupt the shared memory segment and
bring the whole postmaster down. That's what it looks like is
happening. I have no why though.
--
Brad Nicholson 416-673-4106
Database Administrator, Afilias Canada Corp.
