On Tue, Mar 16, 2004 at 01:16:56PM +0530, Shridhar Daithankar wrote:
> I believe using hdparm on linux, one can see whether or not write caching
> is enabled and also set the caching.
>
> I don't think any IDE disk would lie about write caching status. (If one
> does then it is really hard to f
Rod K wrote:
> Does anyone know the equivalent to hdparm on FreeBSD?
Yes, something like:
In FreeBSD, add "hw.ata.wc=0" to /boot/loader.conf.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a h
> [EMAIL PROTECTED]
> Subject: Re: [GENERAL] Data Corruption in case of abrupt failure
>
>
> On Tue, 16 Mar 2004, Tom Lane wrote:
>
> > "Keith C. Perry" <[EMAIL PROTECTED]> writes:
> > > I've read threads like this before and because I've ne
"scott.marlowe" <[EMAIL PROTECTED]> writes:
> On Tue, 16 Mar 2004, Tom Lane wrote:
>> What I'd suggest is to set up a simple test involving a long string of
>> very small transactions (a bunch of separate INSERTs into a table with
>> no indexes works fine). Time it twice, once with "fsync" enabled
On Tue, 16 Mar 2004, Tom Lane wrote:
> "Keith C. Perry" <[EMAIL PROTECTED]> writes:
> > I've read threads like this before and because I've never lost data on
> > servers with IDE drives after doing some basic torture tests
> > (e.g. pulling the plug in the middle of an update et al), I don't
> >
On Wed, 3 Mar 2004, satish satish wrote:
> Hi,
>
> I am trying to do some reliability tests on postgre SQL. I have
> use-case where the power can go off abruptly. I initiated 10,000 insert
> operations and pulled out the cable in the middle. I had auto-commit
> option turned on. I observed 2
