Wed Aug 1 20:15:23 PDT 2007
- Previous message: [Slony1-general] problems with slony1-1.2.10 and postgresql-8.2.4
- Next message: [Slony1-general] problems with slony1-1.2.10 and postgresql-8.2.4
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, 1 Aug 2007, David Rees wrote: > On 8/1/07, Jeff Frost <jeff at frostconsultingllc.com> wrote: >>> When I upgrade I put Postgres / Slony into a unique directory for each >>> build (for example /usr/local/pgsql-8.2.4-2007080101 and >>> /usr/local/slony-1.2.10-2007080101) and then symlink that folder to >>> the same folder name without the version so I don't have to bother >>> updating paths and startup scripts. >> >> I do that as well for the slony installs, but again, postgres is installed via >> rpm. > > I wonder if the 8.2.4 rpm is built on a 64bit machine? I would > recommend compiling both postgresql and slony from source. Devrim, If you're watching this thread, do you care to comment? I don't see why it would matter as a 64-bit machine can make i386 and i686 binaries just as well as x86_64. If I extract the files from the postgresql-server rpm and run file against them, it shows them all as 32-bit executables: initdb: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.5, dynamically linked (uses shared libs), stripped ipcclean: Bourne shell script text executable pg_controldata: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.5, dynamically linked (uses shared libs), stripped pg_ctl: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.5, dynamically linked (uses shared libs), stripped pg_resetxlog: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.5, dynamically linked (uses shared libs), stripped postgres: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.5, dynamically linked (uses shared libs), stripped postmaster: symbolic link to `postgres' The same was true of all the shared modules in /usr/lib/pgsql. Also, "strings * |grep lib64" returned nothing whereas "strings * | grep lib" returns the following interesting tidbits: /usr/lib /usr/lib/pgsql So it really makes no sense to me that it's looking in lib64. More info later when I have another machine to test on. -- Jeff Frost, Owner <jeff at frostconsultingllc.com> Frost Consulting, LLC http://www.frostconsultingllc.com/ Phone: 650-780-7908 FAX: 650-649-1954
- Previous message: [Slony1-general] problems with slony1-1.2.10 and postgresql-8.2.4
- Next message: [Slony1-general] problems with slony1-1.2.10 and postgresql-8.2.4
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list