Re: Lost rows/data corruption? - Mailing list pgsql-general

From Andrew Hall
Subject Re: Lost rows/data corruption?
Date
Msg-id 019401c51546$06c73620$5001010a@bluereef.local
Whole thread Raw
In response to Re: Lost rows/data corruption?  ("Andrew Hall" <temp02@bluereef.com.au>)
Responses Re: Lost rows/data corruption?  (Scott Marlowe <smarlowe@g2switchworks.com>)
List 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@fuhr.org>
To: "Andrew Hall" <temp02@bluereef.com.au>
Cc: "Scott Marlowe" <smarlowe@g2switchworks.com>; "Alban Hertroys"
<alban@magproductions.nl>; "Marco Colombo" <pgsql@esiway.net>;
<pgsql-general@postgresql.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/
>


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: postgresql version on RH workstation 4.0
Next
From: Scott Marlowe
Date:
Subject: Re: Lost rows/data corruption?