From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <rbt(at)rbt(dot)ca>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Win32 Powerfail testing - results |
Date: | 2003-02-03 22:23:46 |
Message-ID: | 03AF4E498C591348A42FC93DEA9661B8259BC4@mail.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: 03 February 2003 21:52
> To: Dave Page
> Cc: rbt(at)rbt(dot)ca; pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] Win32 Powerfail testing - results
>
>
> "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> writes:
> > Rod Taylor allegedly said:
> >> Any change of tossing in a periodic VACUUM or would that throw off
> >> the results?
>
> > Dunno, Tom could best answer that, but a *complete guess* based on
> > piecing together tidbits of how it all works from various threads
> > here, would be that it would merely increase the time period during
> > which a powerfail would be unlikely to cause duplicate
> rows. Reasoning
> > for this is that vacuum would be messing with tuples that
> are already
> > dead.
>
> I think it'd be interesting to try it both ways. VACUUM
> might throw in new failure modes. I'm not sure if it could
> mask the failure mode you already found.
OK, I'll bung Win2K back on the test box tomorrow. Any preference as to
the type of vacuum? I assume full would be most likely to cause
problems. I'll add the vacuum after the commit...
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2003-02-03 22:29:51 | Re: Win32 Powerfail testing - results |
Previous Message | Jan Wieck | 2003-02-03 22:16:35 | Re: win32 port --asynchronous I/O and memory |