From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
Cc: | Christopher Browne <cbbrowne(at)libertyrms(dot)info>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: cvs head? initdb? |
Date: | 2003-11-14 18:12:32 |
Message-ID: | 200311141812.hAEICWe22015@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jan Wieck wrote:
> >> Yeah, there was a problem with *extreme* sharing ... the code tried to
> >> use the same buffer for multiple disk blocks at the same time, and
> >> somehow the backends did not agree on the correct content. But it's
> >> fixed and back in. You can see ARC working by setting
> >>
> >> buffer_strategy_status_interval = 10 # seconds
The above line is the one I was asking about? Does that just control
debug output interval? If so, it should be named more appropriately.
> >>
> >> and starting postmaster with -d1
> >
> > It is not on by default?
> >
>
> Sure not. Why would someone turn on debug messages by default?
>
> Or did you mean ARC itself? Since it replaced the old LRU code, it is
> the only choice you have now. Which sort of raises the question if we
> would want to have multiple choices, like a config option
>
> buffer_replacement_strategy = lru|lru2|arc
No, I don't see much value to this and would encourage people to play
with something that probably is is of little value.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Dann Corbit | 2003-11-14 18:18:19 | Re: INSERT extremely slow with large data sets |
Previous Message | Andrew Dunstan | 2003-11-14 17:50:25 | Re: [HACKERS] heads up -- subtle change of behavior of |