Skip site navigation (1) Skip section navigation (2)

Re: cvs tip - stats buffer process consuming 100% cpu

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Joe Conway <mail(at)joeconway(dot)com>, "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: cvs tip - stats buffer process consuming 100% cpu
Date: 2006-01-03 20:51:11
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> The only guess I have is that select() is modifying the timeout
> structure on return, but I didn't think it did that, does it?

You shouldn't assume so; I think it does on some platforms.  The Single
Unix Spec says

	On successful completion, the object pointed to by the timeout
	argument may be modified. 

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Jim C. NasbyDate: 2006-01-03 21:16:55
Subject: Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and
Previous:From: Jon JensenDate: 2006-01-03 20:00:24
Subject: Re: Why don't we allow DNS names in pg_hba.conf?

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group