Re: [PERFORM] big select is resulting in a large amount of disk writing by kjournald

2009-12-15 Thread Scott Carey
On 12/10/09 8:41 AM, "Kevin Grittner" wrote: > > There has been some talk about possibly writing tuples in a frozen > state with the hint bits already set if they are loaded in the same > database transaction which creates the table, but I'm not aware of > anyone currently working on this. >

Re: [PERFORM] big select is resulting in a large amount of disk writing by kjournald

2009-12-10 Thread Kevin Grittner
Joseph S wrote: > I just installed a shiny new database server with pg 8.4.1 running > on CentOS 5.4. After using slony to replicate over my database I > decided to do some basic performance tests to see how spiffy my > shiny new server is. This machine has 32G ram, over 31 of which > is used for

Re: [PERFORM] big select is resulting in a large amount of disk writing by kjournald

2009-12-09 Thread Joseph S
Greg Smith wrote: Joseph S wrote: Greg Smith wrote: Joseph S wrote: So I run "select count(*) from large_table" and I see in xosview a solid block of write activity. Runtime is 28125.644 ms for the first run. The second run does not show a block of write activity and takes 3327.441 ms http

Re: [PERFORM] big select is resulting in a large amount of disk writing by kjournald

2009-12-09 Thread Greg Smith
Joseph S wrote: Greg Smith wrote: Joseph S wrote: So I run "select count(*) from large_table" and I see in xosview a solid block of write activity. Runtime is 28125.644 ms for the first run. The second run does not show a block of write activity and takes 3327.441 ms http://wiki.postgresql.

Re: [PERFORM] big select is resulting in a large amount of disk writing by kjournald

2009-12-09 Thread Joseph S
Greg Smith wrote: Joseph S wrote: So I run "select count(*) from large_table" and I see in xosview a solid block of write activity. Runtime is 28125.644 ms for the first run. The second run does not show a block of write activity and takes 3327.441 ms http://wiki.postgresql.org/wiki/Hint_Bit

Re: [PERFORM] big select is resulting in a large amount of disk writing by kjournald

2009-12-09 Thread Greg Smith
Joseph S wrote: So I run "select count(*) from large_table" and I see in xosview a solid block of write activity. Runtime is 28125.644 ms for the first run. The second run does not show a block of write activity and takes 3327.441 ms http://wiki.postgresql.org/wiki/Hint_Bits -- Greg Smith

Re: [PERFORM] big select is resulting in a large amount of disk writing by kjournald

2009-12-09 Thread Kenneth Marshall
Hint bit I/O? Ken On Wed, Dec 09, 2009 at 01:29:00PM -0500, Joseph S wrote: > I just installed a shiny new database server with pg 8.4.1 running on > CentOS 5.4. After using slony to replicate over my database I decided to > do some basic performance tests to see how spiffy my shiny new server