| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Marko Kreen <markokr(at)gmail(dot)com>, Jeff Amiel <becauseimjeff(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Out of Memory - 8.2.4 |
| Date: | 2007-08-30 14:10:52 |
| Message-ID: | 20070830141052.GK5872@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane escribió:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > Tom Lane escribió:
> >> BTW, if an autovac worker gets an elog(ERROR) on one table, does it die
> >> or continue on with the next table?
>
> > It continues with the next table if interrupted (SIGINT), but the worker
> > exits on any other error.
>
> Hmm, that seems backwards. What's the rationale?
I don't remember :-( We now use SIGTERM for shutdown, which closes the
worker for good.
It may well be that we need to change this so that the worker is shut
down on specific error codes, instead of continuing on some other codes.
Or it may need more thorough surgery.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2007-08-30 15:13:21 | Re: What kind of locks does vacuum process hold on the db? |
| Previous Message | Tom Lane | 2007-08-30 14:01:12 | Re: Out of Memory - 8.2.4 |