Skip site navigation (1) Skip section navigation (2)

Re: Bug#342369: PostgreSQL 8.1.0 RHEL / Debian incompatible

From: Martin Pitt <martin(at)piware(dot)de>
To: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>,Anand Kumria <wildfire(at)progsoc(dot)uts(dot)edu(dot)au>,Richard van den Berg <richard(dot)vandenberg(at)trust-factory(dot)com>,342369(at)bugs(dot)debian(dot)org, pgsql-general(at)postgresql(dot)org,pgsql-ports(at)postgresql(dot)org
Subject: Re: Bug#342369: PostgreSQL 8.1.0 RHEL / Debian incompatible
Date: 2005-12-13 17:26:29
Message-ID: 20051213172629.GD30925@piware.de (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-ports
Hi Stephen!

Stephen Frost [2005-12-13 11:06 -0500]:
> Honestly, in the end I think the default should be changed.  It could
> fall-back to double with a warning (if it doesn't already) if the
> compiler doesn't support 64bit integers.
> [...]
> I don't think the Debian default should be changed though.  If, say, an
> m68k user actually complained about the default not being the right
> option for them then I'd say we should consider having configure options
> be different for those architectures and not that we should move
> everyone to using doubles.

I fully agree. (BTW, I doubt that double operations on m68k would be
any faster than integer ones...)

Thanks,

Martin

-- 
Martin Pitt        http://www.piware.de
Ubuntu Developer   http://www.ubuntu.com
Debian Developer   http://www.debian.org

In a world without walls and fences, who needs Windows and Gates?

In response to

Responses

pgsql-ports by date

Next:From: Stephan SzaboDate: 2005-12-13 17:49:08
Subject: Re: Bug#342369: PostgreSQL 8.1.0 RHEL / Debian incompatible
Previous:From: Stephen FrostDate: 2005-12-13 16:06:13
Subject: Re: Bug#342369: PostgreSQL 8.1.0 RHEL / Debian incompatible

pgsql-general by date

Next:From: Michael FuhrDate: 2005-12-13 17:28:42
Subject: Re: timestamp <-> ctime conversion question...
Previous:From: Peter L. BergholdDate: 2005-12-13 17:13:33
Subject: triggering on deletes, NEW row or OLD row?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group