Hannu Krosing <hannu(at)tm(dot)ee> writes:
> Have you any ideas how to distinguish between interactive and
> non-interactive disk I/O coming from postgresql backends ?

I don't see how.  For one thing, the backend that originally dirtied
a buffer is not necessarily the one that writes it out.  Even assuming
that we could assign a useful priority to different I/O requests,
how do we tell the kernel about it?  There's no portable API for that
AFAIK.

One thing that would likely help a great deal is to have the WAL files
on a separate disk spindle, but since what I've got is a one-disk
system, I can't test that on this PC.

			regards, tom lane

In response to

• Re: problems with new vacuum (??) at 2002-01-02 10:55:56 from Hannu Krosing

Responses

• Re: problems with new vacuum (??) at 2002-01-02 21:09:14 from Hannu Krosing

pgsql-hackers by date

Next:	From: Tom Lane	Date: 2002-01-02 16:09:34
	Subject: Re: Duplicate-key-detection failure case found in btree
Previous:	From: Matthew T. O'Connor	Date: 2002-01-02 14:49:58
	Subject: Re: problems with new vacuum (??)