Thanks Tom,
Yes, this is beta1, not the CVS tip, so all is golden.
Paul
Tom Lane wrote:
Paul Ramsey <[EMAIL PROTECTED]> writes:
I started the database from "/home/pramsey/pgtest/8.0/bin" using
"./pg_ctl start -D /home/pramsey/pgtest/8.0/data"
Ah-hah ... and this is 8.0beta1, right, not anything l
Paul Ramsey <[EMAIL PROTECTED]> writes:
> I started the database from "/home/pramsey/pgtest/8.0/bin" using
> "./pg_ctl start -D /home/pramsey/pgtest/8.0/data"
Ah-hah ... and this is 8.0beta1, right, not anything later?
I fixed some problems associated with "." and ".." in the executable's
path l
Things definately do not like to be run from within "bin". I added
/home/pramsey/pgtest/8.0/bin to my PATH and then ran everything without
a direct path reference:
[EMAIL PROTECTED] 8.0]$ pg_ctl start -D /home/pramsey/pgtest/8.0/data
postmaster starting
LOG: database system was shut down at 200
Sounds like we are getting close. From strace:
stat64("/home/pramsey/pgtest/8.0/bin/lib/postgresql/plpgsql",
0xbfffe480) = -1 ENOENT (No such file or directory)
stat64("/home/pramsey/pgtest/8.0/bin/lib/postgresql/plpgsql.so",
0xbfffe480) = -1 ENOENT (No such file or directory)
stat64("$libdir/plp
I am afraid it gets crazier...
I put /home/pramsey/pgtest/8.0/bin on my $PATH
Now:
[EMAIL PROTECTED] 8.0]$ pg_config --pkglibdir
/home/pramsey/pgtest/8.0/lib/postgresql
Hm, correct.
[EMAIL PROTECTED] 8.0]$ ./bin/pg_config --pkglibdir
/home/pramsey/pgtest/8.0/./lib/postgresql
Also correct, but getti
Paul Ramsey <[EMAIL PROTECTED]> writes:
> ... It is the actual binaries that seem to not know
> where $libdir is supposed to be.
Where do they think it is?
A useful way to check would be to strace the backend while you're
executing "createlang" or another command that tries to load a
dynamic lib
Ah, what is your $bindir? Is it /home/pramsey/pgtest/8.0/bin/postgresql?
---
Paul Ramsey wrote:
> Check this out!
>
> [EMAIL PROTECTED] bin]$ ./pg_config --pkglibdir
> /home/pramsey/pgtest/8.0/bin/lib/postgresql
>
Check this out!
[EMAIL PROTECTED] bin]$ ./pg_config --pkglibdir
/home/pramsey/pgtest/8.0/bin/lib/postgresql
^^^
And yet:
./port/pg_config_paths.h:#define PKGLIBDIR
"/home/pramsey/pgtest/8.0/lib/postgresql"
Could the problem be here? (port/path.c):
/*
* get_pkglib_pa
The expansions in the build scripts all seem correct, and in fact, all
the libraries are installed in the right place, both the system stuff
(plpgsql.so) and the contrib stuff (libpostgis.so) ends up in
/opt/foo/lib/postgresql. It is the actual binaries that seem to not know
where $libdir is su
Devrim GUNDUZ wrote:
>
> Hi,
>
> On Wed, 18 Aug 2004, Paul Ramsey wrote:
>
> > When installing PgSQL into a non-standard location (like /opt/foo) the
> > configure script decides to install all the contrib libraries and
> > plpglsq into /opt/foo/lib/postgresql. This would be fine, except that
Hi,
On Wed, 18 Aug 2004, Paul Ramsey wrote:
> When installing PgSQL into a non-standard location (like /opt/foo) the
> configure script decides to install all the contrib libraries and
> plpglsq into /opt/foo/lib/postgresql. This would be fine, except that
> backend does not recognize this d
Short bug report:
When installing PgSQL into a non-standard location (like /opt/foo) the
configure script decides to install all the contrib libraries and
plpglsq into /opt/foo/lib/postgresql. This would be fine, except that
backend does not recognize this directory as a place to be searched fo
12 matches
Mail list logo
