Re: sblock state on FreeBSD 6.1
| От | Tom Lane |
|---|---|
| Тема | Re: sblock state on FreeBSD 6.1 |
| Дата | |
| Msg-id | 17513.1146677823@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: sblock state on FreeBSD 6.1 ("Jim C. Nasby" <jnasby@pervasive.com>) |
| Ответы |
Re: sblock state on FreeBSD 6.1
|
| Список | pgsql-hackers |
"Jim C. Nasby" <jnasby@pervasive.com> writes:
> On Tue, May 02, 2006 at 11:06:59PM -0400, Tom Lane wrote:
>> Actually, the stats socket seems like a really good bet to me, since all
>> the backends will be interested in the same socket. The
>> client-to-backend sockets are only touched by two processes each, so
>> don't seem like big contention sources.
> Do we take specific steps to ensure that we don't block when attempting
> to write to these sockets?
Well, we have the socket set to O_NONBLOCK mode. Whether that avoids
the problem you're seeing ...
> BTW, this server does have command string logging on, so if this is a
> stats issue that probably made the problem worse.
Can you turn that off for a bit and see if it affects things?
regards, tom lane
В списке pgsql-hackers по дате отправления: