Either a) modify share/conversion_create.sql to specify a full path or b) modify share/conversion_create.sql to simply remove "$libdir/" everywhere, then setting dynamic_library_path in share/postgresql.conf.sample
allows initdb and createdb to run, which was my initial stumbling block. I haven't done anything in particular with the resulting database yet. Do you expect the installation to break in other places? It would be nice if that $libdir just weren't in the conversion_create.sql at all: it only represents the compiled-in default, which the program knows anyway, and having it there prevents the dynamic_library_path setting from having any effect - at least that's what seems to be happening. I don't what other effects that variable might be having, of course. Thanks. - DAP -----Original Message----- From: Peter Eisentraut [mailto:[EMAIL PROTECTED] Sent: Thursday, July 15, 2004 5:33 PM To: David Parker; [EMAIL PROTECTED] Subject: Re: [GENERAL] moving an installation David Parker wrote: > I need to be able to build postgres (7.4.3) with a given --prefix, but > then pack up the installation directory and deploy it in another > directory (as part of a product install, for instance). > > I configured with --disable-rpath, but I'm still getting the This doesn't work. There are a lot more paths compiled in than just the rpath. If you want to change the installation paths, you need to rebuild from scratch. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
