[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] Approaches to maintain clinical data uptime

From: James Busser
Subject: Re: [Gnumed-devel] Approaches to maintain clinical data uptime
Date: Wed, 3 May 2006 01:04:08 -0700

On May 1, 2006, at 8:53 AM, Karsten Hilbert wrote:
One disc for the OS because... db speed would be improved?
For that you'd have to separate table files and WAL log onto
separate discs

Speaking of write-ahead logs, would these be standard in GNUmed -- as currently deployed under Postgres -- and would these WALs be easily (or only with great difficulty) usable to recover data that had not made it into the secondary (backup) server, between the time of any last primary database backup (dump) and the time of a primary server crash?

Regarding proper backup dumps off the primary server:

- is it recommended or required that the database to be fully logged off, so that it is in an unambiguous or "clean" state (no unprocessed transactions) at the time of the dump?

- can Syan or Karsten, if the work involved is limited, attempt a load test of writing the dump file, so we might know how long this would require and what its size might be... this is pertinent to office procedures and downtime

reply via email to

[Prev in Thread] Current Thread [Next in Thread]