| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Pablo Delgado Díaz-Pache <delgadop(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Autovacuum seems to block database: WARNING worker took too long to start |
| Date: | 2010-11-16 14:49:43 |
| Message-ID: | 1289918622-sup-8461@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Excerpts from Pablo Delgado Díaz-Pache's message of lun nov 15 04:52:53 -0300 2010:
> > But it strikes me that the code comment is wrong in one significant way:
> > if the postmaster were failing to heed SIGUSR1 at all, you could reach
> > the timeout here, because the fork-failed signal wouldn't get sent.
Hmm, yeah, I guess I wasn't considering the idea that postmaster was so
busy with something else that it wouldn't be able to respond to the
launcher's requests. As you say, if it went away entirely, autovacuum
would also suicide.
> > Could you try strace'ing the postmaster process to see what it's doing
> > when this is happening?
>
> I definitely will.
Yes, please.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pablo Delgado Díaz-Pache | 2010-11-16 15:18:09 | Re: Autovacuum seems to block database: WARNING worker took too long to start |
| Previous Message | gdsorin | 2010-11-16 14:25:17 | Re: could not map view of backend variables: error code 6 |