From: Mathias Breuninger <mathias.breuninger@espace29.asso.fr>
To: pgsql-admin@postgresql.org
Subject: Re: Log-Shipping Standby Server: USE_FLOAT8_BYVAL compatibility error
Date: Thu, 6 Sep 2012 09:00:58 +0200
Message-ID: <003c01cd8bfd$5e1cb9a0$1a562ce0$@breuninger@espace29.asso.fr> (raw)
In-Reply-To: <CAFwQ8rd+PLfDEdSQ0ZHyf6vGfeaQn3KqAxU24xGDxJga_FqA0w@mail.gmail.com>
References: <5045b69d.83ac0e0a.36e7.354dSMTPIN_ADDED@mx.google.com>
<5046764E.4050603@ringerc.id.au>
<50471a01.83ac0e0a.3a58.4281SMTPIN_ADDED@mx.google.com>
<CAFwQ8rd+PLfDEdSQ0ZHyf6vGfeaQn3KqAxU24xGDxJga_FqA0w@mail.gmail.com>
On 09/05/2012 4:59 PM, Craig James wrote:
> On Wed, Sep 5, 2012 at 2:21 AM, Mathias Breuninger
> > I wasn't aware of the binary problem with replication.
> > Maybe the PostgreSQL docs should emphasize the architecture
> restriction.
>
> That's sort of what "binary file" means -- a raw, architecture-specific
> representation of data that's optimized for performance and/or space,
> not portability.
>
> Craig
In fact, it is written clearly in the docs (25.2.1 Planning: " In any case the hardware architecture must be the same — shipping from, say, a 32-bit to a 64-bit system will not work."), but I missed it.
So I apologize for the annoyance.
Regards.
--
Mathias
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: mathias.breuninger@espace29.asso.fr
Subject: Re: Log-Shipping Standby Server: USE_FLOAT8_BYVAL compatibility error
In-Reply-To: <003c01cd8bfd$5e1cb9a0$1a562ce0$@breuninger@espace29.asso.fr>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox