From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: more autovacuum fixes |
Date: | 2007-06-20 17:30:54 |
Message-ID: | 20070620173054.GM30369@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Alvaro Herrera wrote:
> Alvaro Herrera wrote:
>
> > Turns out that this problem is not serious at all, because if that
> > palloc() fails, the whole postmaster will exit with a FATAL out of
> > memory message.
> >
> > The problems in the worker code after fork are still an issue though.
>
> It _is_ still an issue -- and a very serious issue at that. If a worker
> fails before getting its entry from the startingWorker pointer, then
> (patched) autovacuum will no longer run any task.
I figured that I could keep the old check there for when the worker
failed, but still add the new signalling mechanism so that a fork()
failure (which I would think is the most likely of all) is taken care of
in a more timely manner.
I've also improved the rest of the code and comments a bit, and the new
code does seem better now. So I'll go ahead and commit it later today.
--
Alvaro Herrera http://www.flickr.com/photos/alvherre/
"Uno puede defenderse de los ataques; contra los elogios se esta indefenso"
Attachment | Content-Type | Size |
---|---|---|
autovacuum-procs-2.patch | text/x-diff | 19.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2007-06-20 19:17:09 | Re: [HACKERS] 'Waiting on lock' |
Previous Message | Tom Lane | 2007-06-20 17:13:54 | Re: [HACKERS] 'Waiting on lock' |