| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PGSTATBUFF: Warning - receive buffer full |
| Date: | 2004-05-12 22:56:11 |
| Message-ID: | 29671.1084402571@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> writes:
> May 12 15:15:51 gnvdb01 postgres[801]: [75] LOG: PGSTATBUFF: Warning -
> receive buffer full
> given the archives seem to have no mention of this error, I'm just
> curious as to what it actually means if its something I should be
> concerned about.. ie. will it lead to problems somewhere down the line.
It means the pgstats subprocess fell far enough behind to drop some
data. This is the designed behavior under heavy load, so it doesn't
bother me particularly. I think the worst known consequence is bogus
entries in pg_stat_activity (eg, if the stats process missed a
backend-exiting message, it would continue to show that backend as
present in pg_stat_activity, until some other backend starts in the
same BackendId slot).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory S. Williamson | 2004-05-13 00:53:05 | Re: dbmirror |
| Previous Message | Robert Treat | 2004-05-12 21:03:27 | PGSTATBUFF: Warning - receive buffer full |