Re: Lost rows/data corruption?

From: "Andrew Hall" <temp02(at)bluereef(dot)com(dot)au>
To: "Michael Fuhr" <mike(at)fuhr(dot)org>
Cc: "Scott Marlowe" <smarlowe(at)g2switchworks(dot)com>, "Alban Hertroys" <alban(at)magproductions(dot)nl>, "Marco Colombo" <pgsql(at)esiway(dot)net>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: Lost rows/data corruption?
Date: 2005-02-17 23:11:35
Message-ID: 019401c51546$06c73620$5001010a@bluereef.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

We do the maintenance reboot (and other various log cleanups etc) as part of
our normal maintenance practice. We don't really 'need' to do this, however
we've traditionally found that operating systems perform better with an
occassional reboot (cleanup fragmented memory etc.).

----- Original Message -----
From: "Michael Fuhr" <mike(at)fuhr(dot)org>
To: "Andrew Hall" <temp02(at)bluereef(dot)com(dot)au>
Cc: "Scott Marlowe" <smarlowe(at)g2switchworks(dot)com>; "Alban Hertroys"
<alban(at)magproductions(dot)nl>; "Marco Colombo" <pgsql(at)esiway(dot)net>;
<pgsql-general(at)postgresql(dot)org>
Sent: Friday, February 18, 2005 1:56 AM
Subject: Re: [GENERAL] Lost rows/data corruption?

> On Thu, Feb 17, 2005 at 07:40:25PM +1100, Andrew Hall wrote:
>>
>> We have an automated maintenance process that reboots all our
>> customers machines every 10 days at 2am.
>
> What's the purpose of doing this? If it's necessary then the reboots
> aren't really fixing anything. Is whatever problem that prompted
> this procedure being investigated so a permanent fix can be applied?
>
> --
> Michael Fuhr
> http://www.fuhr.org/~mfuhr/
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Scott Marlowe 2005-02-17 23:23:25 Re: Lost rows/data corruption?
Previous Message Tom Lane 2005-02-17 21:37:04 Re: postgresql version on RH workstation 4.0