Re: WAL file compatibility

From: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Radamanthus Batnag <rad(dot)batnag(at)devex(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: WAL file compatibility
Date: 2009-10-21 04:39:04
Message-ID: 3073cc9b0910202139s4b00a57sd908ec10910fdedf@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Tue, Oct 20, 2009 at 10:56 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> writes:
>> On Tue, Oct 20, 2009 at 9:25 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> OS per se shouldn't matter
>
>> unless you try to do it between windows and some flavor of linux
>
> hmmm ... even there, the only risk factor I see would be incompatible
> locale behaviors, which you could avoid by making sure to use C locale
> on both sides.  That could possibly be an issue between any two OSes,
> I suppose.
>

mmm... i was convinced windows had diferences in binary files just
like on text files (ie: in text files there are differences because of
the EOL character) but a litlle test seems to confirm that a WAL file
generated on windows could be read on linux.

--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message stefan 2009-10-21 07:05:02 Re: How to troubleshoot a halted postgres 8.3 ?
Previous Message Scott Marlowe 2009-10-21 03:14:39 Re: Vacuum Full - stops responding(?)