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

Re: can't handle large number of INSERT/UPDATEs

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Anjan Dave" <adave(at)vantage(dot)com>
Cc: "Matt Clark" <matt(at)ymogen(dot)net>, "Rod Taylor" <pg(at)rbt(dot)ca>,"Postgresql Performance" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: can't handle large number of INSERT/UPDATEs
Date: 2004-10-26 22:37:32
Message-ID: 14215.1098830252@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-performance
"Anjan Dave" <adave(at)vantage(dot)com> writes:
> One thing I am not sure is why 'bi' (disk writes) stays at 0 mostly,
> it's the 'bo' column that shows high numbers (reads from disk). With so
> many INSERT/UPDATEs, I would expect it the other way around...

Er ... it *is* the other way around.  bi is blocks in (to the CPU),
bo is blocks out (from the CPU).

			regards, tom lane

In response to

Responses

pgsql-performance by date

Next:From: Anjan DaveDate: 2004-10-26 22:45:37
Subject: Re: can't handle large number of INSERT/UPDATEs
Previous:From: John MeinelDate: 2004-10-26 22:21:35
Subject: Re: Sequential Scan with LIMIT

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