| From: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: autovacuum cannot start when connection is full |
| Date: | 2006-08-25 08:51:10 |
| Message-ID: | 20060825174243.55E5.ITAGAKI.TAKAHIRO@oss.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com> wrote:
> There is a mention in autovacuum doc:
> http://www.postgresql.org/docs/8.1/interactive/maintenance.html#AUTOVACUUM
>
> Last sentence of the first paragraph is:
> "Also, it's important to allow a slot for the autovacuum process when
> choosing the value of superuser_reserved_connections."
Thank you!
It may be as well to add the same mention to the description of
superuser_reserved_connections.
| Determines the number of connection "slots" that are reserved for connections
| by PostgreSQL superusers, *including autovacuum*.
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2006-08-25 09:05:52 | Re: Tricky bugs in concurrent index build |
| Previous Message | Böszörményi Zoltán | 2006-08-25 07:31:42 | Performance testing of COPY (SELECT) TO |