LinkedIn
I'd like to add you to my professional network on LinkedIn.
- Michael Clemmons
Confirm that you know Michael Clemmons
https://www.linkedin.com/e/isd/1082803004/E81w7LvD/
--
(c) 2010, LinkedIn Corporation
Jeff wrote:
while(true)
{
if buffers_written > bgwriter_lru_maxpages
or buffers_written > anticipated_pages_needed *
bgwriter_lru_multiplier
{
sleep(bgwriter_delay ms)
continue;
}
...
}
so I should not be able to have more than ~5000 bgwriter_clean pages
On Wed, 2010-02-17 at 08:30 -0500, Jeff wrote:
> Since getting on 8.4 I've been monitoring things fairly closely.
> I whipped up a quick script to monitor pg_stat_bgwriter and save
> deltas every minute so I can ensure my bgwriter is beating out the
> backends for writes (as it is supposed to d
Vacuum Full Verbose did not get the disk space back to OS, it did bloat my
indexes, also got out of memory error. I dumped the suspicious table,
deleted it, re-created it, then restored the data and re-indexed the data,
so I got the disk space back.
To avoid the database eating up the disk space
On Feb 15, 2010, at 1:25 PM, Rose Zhou wrote:
> Thanks Ben:
>
> I will adjust the auto vacuum parameters. It is on now, maybe not frequently
> enough.
> How to get the disk space back to OS? Will a Vacuum Full Verbose get the disk
> space back to OS?
>
>
Yes, but it might bloat your index
Since getting on 8.4 I've been monitoring things fairly closely.
I whipped up a quick script to monitor pg_stat_bgwriter and save
deltas every minute so I can ensure my bgwriter is beating out the
backends for writes (as it is supposed to do).
Now, the odd thing I'm running into is this:
bg
Joshua D. Drake wrote:
On Thu, 2010-02-11 at 12:39 +, Matthew Wakeling wrote:
Just a heads up - apparently the more recent Dell RAID controllers will no
longer recognise hard discs that weren't sold through Dell.
http://www.channelregister.co.uk/2010/02/10/dell_perc_11th_gen_qualified_hdds
