From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Tatsuo Ishii" <t-ishii(at)sra(dot)co(dot)jp> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Win32 Powerfail testing |
Date: | 2003-03-07 08:18:47 |
Message-ID: | 03AF4E498C591348A42FC93DEA9661B8259D27@mail.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> -----Original Message-----
> From: Tatsuo Ishii [mailto:t-ishii(at)sra(dot)co(dot)jp]
> Sent: 07 March 2003 01:33
> To: Dave Page
> Cc: pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] Win32 Powerfail testing
>
>
> > > As I said in the previlus mails, open()+_commit() does the
> > > right job with the transaction log files. So probably I think
> > > I should stick with open()+_commit() approach for ordinary
> > > table/index files too.
> >
> > Oh, I didn't see that message. So it's either:
> >
> > open() + _commit()
>
> Sorry, I did not mention it explicitly. I meant we use the
> same implementation as Jan's work. He uses open()+_commit(),
> I believe.
Ah, but Jan/Katie's code *did not* survive the powerfails. Is there a
relatively easy way we can test open()/_commit against
CreateFile()/FlushFileBuffers() with the FILE_FLAG_WRITE_THROUGH flag as
suggested by Magnus (and indirectly by Merlin I guess)?
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2003-03-07 08:37:09 | Re: Win32 Powerfail testing |
Previous Message | Kevin Brown | 2003-03-07 07:07:52 | Re: stats_command_string default? |