From: | Kokas Zsolt <kokas(dot)zsolt(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | embedded pgsql media-failure |
Date: | 2009-02-03 11:03:11 |
Message-ID: | ce82ada0902030303w58b9d665g7da69293b79225c8@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi!
I'd need some advice.
I'm working on a quite special field, I have to set up an embedded DB,
which will store logs (measured values) and gives configuration to the
machine and alsothis configuration can be changed.
The system will consist of a CF card (with wear leveling) and an Intel
atom CPU. The config data and the measured values together will take
up around 2-3000 rows + a couple of ten thousand rows.
The businees's side wants to make it as secure as it is possible,
meaning, that the CF card will have two partitions, and the DB should
be mirrored or distributed somehow on this two partiton, in case of a
one-point disk-error the system should stay stable.
Even though I've never used them, but as I see is, that "standard"
replication like Slony, Heartbeat+DRBD or Postgres-R are not really
able to cope with such kind of setup. Maybe I got something wrong :)
So my problem is: without a network, on one single CF card with two
partitions and only one CPU and only one server running how can it be
managed to protect the data part against media-failure.
Thanks for your help!
_______________________________
Kokas Zsolt
Save a tree...please only print this e-mail if it is genuinely required.
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Markus | 2009-02-03 11:20:52 | Re: embedded pgsql media-failure |
Previous Message | Scott Marlowe | 2009-02-03 09:08:54 | Re: calculating elapsed times between timestamps |