Re: [PERFORM] Identifying the nature of blocking I/O

2008-08-25 Thread Jonah H. Harris
On Fri, Aug 22, 2008 at 7:52 AM, Peter Schuller <[EMAIL PROTECTED]> wrote: > Is there currently a way of dumping such information? I.e., asking PG > "what are backends waiting on right now?". Unfortunately, not within Postgres itself. The question, "what is the database waiting on?" is a good one

Re: [PERFORM] Big delete on big table... now what?

2008-08-25 Thread Fernando Hevia
> Gregory Stark <[EMAIL PROTECTED]> writes: > > "Bill Moran" <[EMAIL PROTECTED]> writes: > > > "Fernando Hevia" <[EMAIL PROTECTED]> wrote: > >> Hi list. > >> I have a table with over 30 million rows. Performance was dropping > >> steadily so I moved old data not needed online to an > historic t

Re: [PERFORM] Identifying the nature of blocking I/O

2008-08-25 Thread RW
This matches not exactly the topic but it is sometimes helpfull. If you've enabled I/O accounting and a kernel >= 2.6.20 (needs to be compiled with **CONFIG_TASKSTATS=y CONFIG_TASK_DELAY_ACCT=y CONFIG_TASK_XACCT=y CONFIG_TASK_IO_ACCOUNTING=y ) and sysstat package (>= 7.1.5) installed you can use

Re: [PERFORM] Identifying the nature of blocking I/O

2008-08-25 Thread Alexander Staubo
On Mon, Aug 25, 2008 at 3:34 AM, Scott Carey <[EMAIL PROTECTED]> wrote: > DTrace is available now on MacOSX, Solaris 10, OpenSolaris, and FreeBSD. > Linux however is still in the dark ages when it comes to system monitoring, > especially with I/O. While that's true, newer 2.6 kernel versions at le