On Wednesday 10 March 2010 18:32:41 Scott Marlowe wrote:
> On Tue, Mar 9, 2010 at 11:49 PM, Phillip Berry
>
> wrote:
> > Hi Everyone,
> >
> > We're in the market for a new DB server to replace our current one (yes
> > it's one of *those* questions) ;
Hi Everyone,
We're in the market for a new DB server to replace our current one (yes it's
one of *those*
questions) ;).
It'll have quad core Xeons, 36GB RAM and some sort of Raid 10 configuration.
Our provider is pushing us towards 6 x SATA II disks in a Raid 10 configuration
or 4 x SAS disks
or even
negative returns by setting the fsm too high?
Cheers
Phil
On Wednesday 17 December 2008 13:02:21 Grzegorz Jaśkiewicz wrote:
> On Wed, Dec 17, 2008 at 12:55 AM, Phillip Berry
>
> wrote:
> > I thought 185K was pretty high, is going to 700K+ reasonable? I've got
Hi Everyone,
Just wondering what the maximum reasonable free space map setting should be?
I'm receiving the
following advice from vacuum:
INFO: free space map contains 170803 pages in 117 relations
DETAIL: A total of 185000 page slots are in use (including overhead).
733008 page slots are re
On Friday 12 December 2008 03:59:42 Tom Lane wrote:
> Greg Smith writes:
> > On Thu, 11 Dec 2008, Phillip Berry wrote:
> >> I'm not running PITR and checkpoint_segments is set to 100 as this is
> >> home to a very write intensive app.
> >
> > That'
Thursday 11 December 2008 15:20:21 you wrote:
> On Thu, 11 Dec 2008, Phillip Berry wrote:
> > I've got a bit of a problem. It started last night when postgres
> > (8.1.9) went down citing the need for a vacuum full to be done due to
> > the transaction log needing to
Hello Everyone,
I've got a bit of a problem. It started last night when postgres (8.1.9) went
down citing the need
for a vacuum full to be done due to the transaction log needing to wraparound.
So I stopped the server, logged in using a standalone backend and started a
vacuum full analyze on
