Re: understanding postgres issues/bottlenecks - Mailing list pgsql-performance

From Luke Lonergan
Subject Re: understanding postgres issues/bottlenecks
Date
Msg-id 2106D8DC89010842BABA5CD03FEA406168A731D3@EXVMBX018-10.exch018.msoutlookonline.net
Whole thread Raw
In response to understanding postgres issues/bottlenecks  (Stefano Nichele <stefano.nichele@gmail.com>)
Responses Re: understanding postgres issues/bottlenecks  ("Scott Marlowe" <scott.marlowe@gmail.com>)
Re: understanding postgres issues/bottlenecks  ("M. Edward (Ed) Borasky" <znmeb@cesmail.net>)
List pgsql-performance
Not to mention the #1 cause of server faults in my experience: OS kernel bug causes a crash.  Battery backup doesn't
helpyou much there.
 

Fsync of log is necessary IMO.

That said, you could use a replication/backup strategy to get a consistent snapshot in the past if you don't mind
losingsome data or can recreate it from backup elsewhere.
 

I think a strategy that puts the WAL on an SLC SSD is a very good one as of Jan/09 and will get much better in short
order.

- Luke

----- Original Message -----
From: pgsql-performance-owner@postgresql.org <pgsql-performance-owner@postgresql.org>
To: Glyn Astill <glynastill@yahoo.co.uk>
Cc: Ron <rjpeace@earthlink.net>; Scott Marlowe <scott.marlowe@gmail.com>; pgsql-performance@postgresql.org
<pgsql-performance@postgresql.org>
Sent: Sun Jan 11 15:35:22 2009
Subject: Re: [PERFORM] understanding postgres issues/bottlenecks

On Sun, 11 Jan 2009, Glyn Astill wrote:

> --- On Sun, 11/1/09, Scott Marlowe <scott.marlowe@gmail.com> wrote:
>
>> They also told me we could never lose power in the hosting
>> center
>> because it was so wonder and redundant and that I was
>> wasting my time.
>
> We'll that's just plain silly, at the very least there's always going to
> be some breakers / fuzes in between the power and the machines.
>
> In fact in our building there's quite a few breaker points between our
> comms room on the 3rd floor and the ups / generator in the basement.
> It's a crappy implementation actually.

the response I get from people is that they give their servers redundant
poewr supplies and put them on seperate circuits so they must be safe from
that.

but as commented, that's not enough in the real world.

David Lang

--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance

pgsql-performance by date:

Previous
From: david@lang.hm
Date:
Subject: Re: understanding postgres issues/bottlenecks
Next
From: "M. Edward (Ed) Borasky"
Date:
Subject: Re: block device benchmarking