Stuart Bishop a écrit :
> If your application is normally reliable, I think the best, cheapest and
> simplest way of keeping the system online when you are on leave is to give
> your work the phone number of a company offering PostgreSQL support
> services. I would avoid adding the extra complexity and additional support
> and maintenance burdens unless you really need it - can work afford to be
> without the system for a day if it crashes? And do you expect it to happen
> infrequently enough that the outages will not be a problem? The advantage of
> having a human available to restore functionality is that they will be able
> to deal with the situations you haven't thought of, whereas an automated
> solution will likely only deal with the situations you have thought of as
> well as making the system more complex, thus creating more things that could
> go wrong.
I agree with you, but I will have two servers : one will be the
file server, the primary controller of the active directory, and
the backup of postgresql; the other one will be the postgresql
server and the backup of the file server and active directory.
So restoring from this situation does not only require postgresql
knoledge, it requires a full understanding of our network
structure, applications, configurations, etc...
But you have a point that having a contact for postgresql support
is a very good idea anyway !
--
Arnaud
