pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Medi Montaseri <montaseri@gmail.com>
To: Chris Browne <cbbrowne@acm.org>
Cc: pgsql-admin@postgresql.org
Subject: Re: Migrating from 32 to 64 bit
Date: Mon, 26 Nov 2007 10:52:52 -0800
Message-ID: <8078a1730711261052i1e904ce7rdb545aade244b666@mail.gmail.com> (raw)
In-Reply-To: <60r6iddmhj.fsf@dba2.int.libertyrms.com>
References: <4748B148.6050001@lncsa.com>
	<474971C0.3090503@theendofthetunnel.de>
	<8078a1730711252124uc5e0cbdpdc7807d92480645b@mail.gmail.com>
	<60r6iddmhj.fsf@dba2.int.libertyrms.com>

I agree with you practical points....I qualified my comments by
saying....theoretically speaking....

Cheers
Medi

On Nov 26, 2007 8:01 AM, Chris Browne <cbbrowne@acm.org> wrote:

> montaseri@gmail.com ("Medi Montaseri") writes:
> > But theoretically speaking, 32 or 64-bit ness of the application (ie the
> postmaster server) should not influence the data types offered by a
> particular DB
> > version. That is the semantics of data types and cpu-arch (register
> width, big endian, little endian, sparc, mips, x86), etc ) offered by a
> particular DB
> > version should be orthogonal.
> > A practical example is when I first begin my business on a Mac, then I
> move the database to a Sun and then on to a mainframe....
>
> That's well and fine, but the point is that when those (reasonably
> generic!) data types get compiled into code for a particular platform,
> with particular endianness and word size, how it is optimal to
> represent them will vary based on the characteristics of the platform.
>
> As a result, not only do you need different executable binaries each
> platform, but you also need different binary database structures on
> each platform.
>
> A conceptually mitigating factor should be that by the time you get
> around to changing platforms, there will likely be a Newer, Better,
> Major PostgreSQL version available.  So you should be considering
> doing a migration from "old, slower, inferior version on the inferior
> platform" to the "better, stronger, faster version on the superior
> platform."  With THAT context, the need to run initdb is further
> "given."
> --
> output = ("cbbrowne" "@" "linuxdatabases.info")
> http://www3.sympatico.ca/cbbrowne/x.html
> "Have  you noticed   that,  when we were   young,  we were   told that
> `everybody else   is doing  it' was   a  really  stupid reason  to  do
> something,  but now it's the standard  reason for picking a particular
> software package?" -- Barry Gehm
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>       choose an index scan if your joining column's datatypes do not
>       match
>

view thread (8+ messages)

Message-ID: <8078a1730711261052i1e904ce7rdb545aade244b666@mail.gmail.com>
Permalink:  ../8078a1730711261052i1e904ce7rdb545aade244b666@mail.gmail.com/
Also on:    postgresql.org/message-id/8078a1730711261052i1e904ce7rdb545aade244b666@mail.gmail.com

 · 

reply

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: montaseri@gmail.com, cbbrowne@acm.org
  Subject: Re: Migrating from 32 to 64 bit
  In-Reply-To: <8078a1730711261052i1e904ce7rdb545aade244b666@mail.gmail.com>

* 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