pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Log-Shipping Standby Server: USE_FLOAT8_BYVAL compatibility error
7+ messages / 5 participants
[nested] [flat]

* Log-Shipping Standby Server: USE_FLOAT8_BYVAL compatibility error
@ 2012-09-04 08:04  Mathias Breuninger <mathias.breuninger@espace29.asso.fr>
  0 siblings, 1 reply; 7+ messages in thread

From: Mathias Breuninger @ 2012-09-04 08:04 UTC (permalink / raw)
  To: pgsql-admin

Hi,

I configure PostgreSQL 9.1.5 on two servers: one with FreeBSD-9.0/powerpc64 and the other with FreeBSD-9.0/powerpc.

The 64 bits server is the master and I tried to configure the 32 bits one as a standby server.

I followed the documentation but I can't start the standby postgres daemon:
 postgres[73978]: [1-1] FATAL:  database files are incompatible with server
 postgres[73978]: [1-2] DETAIL:  The database cluster was initialized with USE_FLOAT8_BYVAL but the server was compiled without USE_FLOAT8_BYVAL.
 postgres[73978]: [1-3] HINT:  It looks like you need to recompile or initdb.

I can't find an option to initialize the database cluster without the USE_FLOAT8_BYVAL.

I can recompile PostgreSQL on the 64bit architecture without this configure option, but I wonder if there will be a performance drawback.

Maybe should I go with Slony-I as it seems to work with differents architectures.

Have you a suggestion/solution?

--
Mathias







^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* Re: Log-Shipping Standby Server: USE_FLOAT8_BYVAL compatibility error
@ 2012-09-04 09:15  Sergey Konoplev <sergey.konoplev@postgresql-consulting.com>
  0 siblings, 0 replies; 7+ messages in thread

From: Sergey Konoplev @ 2012-09-04 09:15 UTC (permalink / raw)
  To: Mathias Breuninger <mathias.breuninger@espace29.asso.fr>; +Cc: pgsql-admin

On Tue, Sep 4, 2012 at 12:04 PM, Mathias Breuninger
<mathias.breuninger@espace29.asso.fr> wrote:
> I configure PostgreSQL 9.1.5 on two servers: one with FreeBSD-9.0/powerpc64 and the other with FreeBSD-9.0/powerpc.
>
> The 64 bits server is the master and I tried to configure the 32 bits one as a standby server.

It can not be run between different architectures and between
different major versions.

>
> I followed the documentation but I can't start the standby postgres daemon:
>  postgres[73978]: [1-1] FATAL:  database files are incompatible with server
>  postgres[73978]: [1-2] DETAIL:  The database cluster was initialized with USE_FLOAT8_BYVAL but the server was compiled without USE_FLOAT8_BYVAL.
>  postgres[73978]: [1-3] HINT:  It looks like you need to recompile or initdb.
>
> I can't find an option to initialize the database cluster without the USE_FLOAT8_BYVAL.
>
> I can recompile PostgreSQL on the 64bit architecture without this configure option, but I wonder if there will be a performance drawback.
>
> Maybe should I go with Slony-I as it seems to work with differents architectures.
>
> Have you a suggestion/solution?
>
> --
> Mathias
>
>
>
>
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin



-- 
Sergey Konoplev

a database architect, software developer at PostgreSQL-Consulting.com
http://www.postgresql-consulting.com

Jabber: gray.ru@gmail.com Skype: gray-hemp Phone: +79160686204




^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* Re: Log-Shipping Standby Server: USE_FLOAT8_BYVAL compatibility error
@ 2012-09-04 09:27  Albe Laurenz <laurenz.albe@wien.gv.at>
  parent: Mathias Breuninger <mathias.breuninger@espace29.asso.fr>
  0 siblings, 0 replies; 7+ messages in thread

From: Albe Laurenz @ 2012-09-04 09:27 UTC (permalink / raw)
  To: Mathias Breuninger *EXTERN* <mathias.breuninger@espace29.asso.fr>; pgsql-admin

Mathias Breuninger wrote:
> I configure PostgreSQL 9.1.5 on two servers: one with FreeBSD-9.0/powerpc64 and the other with
> FreeBSD-9.0/powerpc.
> 
> The 64 bits server is the master and I tried to configure the 32 bits one as a standby server.
> 
> I followed the documentation but I can't start the standby postgres daemon:
>  postgres[73978]: [1-1] FATAL:  database files are incompatible with server
>  postgres[73978]: [1-2] DETAIL:  The database cluster was initialized with USE_FLOAT8_BYVAL but the
> server was compiled without USE_FLOAT8_BYVAL.
>  postgres[73978]: [1-3] HINT:  It looks like you need to recompile or initdb.
> 
> I can't find an option to initialize the database cluster without the USE_FLOAT8_BYVAL.
> 
> I can recompile PostgreSQL on the 64bit architecture without this configure option, but I wonder if
> there will be a performance drawback.

You cannot have primary and standby server with different architectures.

> Maybe should I go with Slony-I as it seems to work with differents architectures.

That's an option.

Yours,
Laurenz Albe


^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* Re: Log-Shipping Standby Server: USE_FLOAT8_BYVAL compatibility error
@ 2012-09-04 21:44  Craig Ringer <ringerc@ringerc.id.au>
  0 siblings, 2 replies; 7+ messages in thread

From: Craig Ringer @ 2012-09-04 21:44 UTC (permalink / raw)
  To: Mathias Breuninger <mathias.breuninger@espace29.asso.fr>; +Cc: pgsql-admin

On 09/04/2012 06:04 PM, Mathias Breuninger wrote:
> Hi,
>
> I configure PostgreSQL 9.1.5 on two servers: one with FreeBSD-9.0/powerpc64 and the other with FreeBSD-9.0/powerpc.
>
> The 64 bits server is the master and I tried to configure the 32 bits one as a standby server.

That isn't a supported configuration. The standby needs to be the same 
architecture as the master and needs to use the same compilation options.

I'm surprised the error message wasn't more useful in this case.

> I can recompile PostgreSQL on the 64bit architecture without this configure option, but I wonder if there will be a performance drawback.

It still won't work. If you want to replicate from a 64-bit machine to a 
32-bit machine you will need to build a 32-bit version of PostgreSQL on 
the 64-bit machine.

--
Craig Ringer




^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* Re: Log-Shipping Standby Server: USE_FLOAT8_BYVAL compatibility error
@ 2012-09-05 09:21  Mathias Breuninger <mathias.breuninger@espace29.asso.fr>
  parent: Craig Ringer <ringerc@ringerc.id.au>
  1 sibling, 0 replies; 7+ messages in thread

From: Mathias Breuninger @ 2012-09-05 09:21 UTC (permalink / raw)
  To: pgsql-admin

On 09/04/2012 11:45 PM CEST, Craig Ringer wrote:
> > The 64 bits server is the master and I tried to configure the 32 bits
> one as a standby server.
> 
> That isn't a supported configuration. The standby needs to be the same
> architecture as the master and needs to use the same compilation
> options.
> 
> I'm surprised the error message wasn't more useful in this case.
> 
> > I can recompile PostgreSQL on the 64bit architecture without this
> configure option, but I wonder if there will be a performance drawback.
> 
> It still won't work. If you want to replicate from a 64-bit machine to
> a 32-bit machine you will need to build a 32-bit version of PostgreSQL
> on the 64-bit machine.
> 
> --
> Craig Ringer

Thank you for your answers.

I wasn't aware of the binary problem with replication.
Maybe the PostgreSQL docs should emphasize the architecture restriction.

I'll explore the other solutions.

--
Mathias





^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* Re: Log-Shipping Standby Server: USE_FLOAT8_BYVAL compatibility error
@ 2012-09-05 14:58  Craig James <cjames@emolecules.com>
  parent: Craig Ringer <ringerc@ringerc.id.au>
  1 sibling, 1 reply; 7+ messages in thread

From: Craig James @ 2012-09-05 14:58 UTC (permalink / raw)
  To: Mathias Breuninger <mathias.breuninger@espace29.asso.fr>; +Cc: pgsql-admin

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




^ permalink  raw  reply  [nested|flat] 7+ messages in thread

* Re: Log-Shipping Standby Server: USE_FLOAT8_BYVAL compatibility error
@ 2012-09-06 07:00  Mathias Breuninger <mathias.breuninger@espace29.asso.fr>
  parent: Craig James <cjames@emolecules.com>
  0 siblings, 0 replies; 7+ messages in thread

From: Mathias Breuninger @ 2012-09-06 07:00 UTC (permalink / raw)
  To: pgsql-admin

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





^ permalink  raw  reply  [nested|flat] 7+ messages in thread


end of thread, other threads:[~2012-09-06 07:00 UTC | newest]

Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2012-09-04 08:04 Log-Shipping Standby Server: USE_FLOAT8_BYVAL compatibility error Mathias Breuninger <mathias.breuninger@espace29.asso.fr>
2012-09-04 09:27 ` Albe Laurenz <laurenz.albe@wien.gv.at>
2012-09-04 09:15 Re: Log-Shipping Standby Server: USE_FLOAT8_BYVAL compatibility error Sergey Konoplev <sergey.konoplev@postgresql-consulting.com>
2012-09-04 21:44 Re: Log-Shipping Standby Server: USE_FLOAT8_BYVAL compatibility error Craig Ringer <ringerc@ringerc.id.au>
2012-09-05 09:21 ` Mathias Breuninger <mathias.breuninger@espace29.asso.fr>
2012-09-05 14:58 ` Craig James <cjames@emolecules.com>
2012-09-06 07:00   ` Mathias Breuninger <mathias.breuninger@espace29.asso.fr>

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