That's the plan, but it's essentially a client managed embedded database so
small steps needed. If I can prove it's the hardware first that would be
preferable.

It looks like diskcheck.pl doesn't work on Windows (no IO::Handle::sync) -
does anybody know of an alternative testkit. A C one would be the best I
suppose as it could exactly mimic PostgreSQL.

Cheers,

James Sewell,
PostgreSQL Team Lead / Solutions Architect



Suite 112, Jones Bay Wharf, 26-32 Pirrama Road, Pyrmont NSW 2009
*P *(+61) 2 8099 9000 <(+61)%202%208099%209000>  *W* www.jirotech.com  *F *
(+61) 2 8099 9099 <(+61)%202%208099%209000>

On Wed, Feb 15, 2017 at 4:10 AM, Magnus Hagander <mag...@hagander.net>
wrote:

> On Tue, Feb 14, 2017 at 5:21 AM, James Sewell <james.sew...@jirotech.com>
> wrote:
>
>> Hello All,
>>
>> I am working with a client who is facing issues with database corruption
>> after a physical hard power off (the machines are at remote sites, this
>> could be a power outage or user error).
>>
>> They have an environment made up of many of the following consumer grade
>> stand alone machines:
>>
>>    - Windows 7 SP1
>>    - PostgreSQL 9.2.4
>>
>>
> If you're using 9.2.4, you are missing about 4 years worth of bugfixes.
> While what you're talking aobut sounds like other issues, you should really
> upgrade that to something that doesn't have loads of known bugs and then
> re-run the tests.
>
> --
>  Magnus Hagander
>  Me: http://www.hagander.net/
>  Work: http://www.redpill-linpro.com/
>

-- 

------------------------------
The contents of this email are confidential and may be subject to legal or 
professional privilege and copyright. No representation is made that this 
email is free of viruses or other defects. If you have received this 
communication in error, you may not copy or distribute any part of it or 
otherwise disclose its contents to anyone. Please advise the sender of your 
incorrect receipt of this correspondence.

Reply via email to