Re: understanding postgres issues/bottlenecks

Not to mention the #1 cause of server faults in my experience: OS kernel bug causes a crash. Battery backup doesn't help you 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 losing some 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(at)postgresql(dot)org <pgsql-performance-owner(at)postgresql(dot)org>
To: Glyn Astill <glynastill(at)yahoo(dot)co(dot)uk>
Cc: Ron <rjpeace(at)earthlink(dot)net>; Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>; pgsql-performance(at)postgresql(dot)org <pgsql-performance(at)postgresql(dot)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(dot)marlowe(at)gmail(dot)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(at)postgresql(dot)org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance