The following bug has been logged online:
Bug reference: 1072
Logged by: Thomas Borg Salling
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system: Red Hat Linux (2.4.20-20.7)
Description:"$libdir/ascii_and_mic": No such file or directory
Deta
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> I have downloaded and built Postgres 7.4.1:
> as user 'tbs':
> ./configure --prefix=/opt/postgres-7.4.1/ --with-perl --enable-thread-safety
> make
> make check
Did the "make check" work?
> creating conversions... ERROR: could not access file
Hi Tom,
The make check worked fine (log attached).
ascii_and_mic.so lives i /opt/postgres-7.4.1/lib, and ldd yields:
[EMAIL PROTECTED] lib]# ldd ascii_and_mic.so
libc.so.6 => /lib/i686/libc.so.6 (0x4200)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x8000)
the complete co
"Thomas Borg Salling" <[EMAIL PROTECTED]> writes:
> ascii_and_mic.so lives i /opt/postgres-7.4.1/lib, and ldd yields:
> [EMAIL PROTECTED] lib]# ldd ascii_and_mic.so=20
> libc.so.6 =3D> /lib/i686/libc.so.6 (0x4200)
> /lib/ld-linux.so.2 =3D> /lib/ld-linux.so.2 (0x8000)
Hmm,
Hi again,
Running ldd as postgres yields the same as root:
[EMAIL PROTECTED] postgres]$ ldd /opt/postgres-7.4.1/lib/ascii_and_mic.so
libc.so.6 => /lib/i686/libc.so.6 (0x4200)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x8000)
the problem occurs when initdb tries to run th
"Thomas Borg Salling" <[EMAIL PROTECTED]> writes:
> for some reason - conversion_create.sql the $libdir is not defined. I tried
> to print $libdir from bin/initdb, but this variable is empty.
$libdir is not an environment variable, it's a notation specially
recognized by CREATE FUNCTION. It shoul
Hi Tom,
I didn't change my mind about prefix. I have tried to do everything by the
book.
[EMAIL PROTECTED] postgres]$ pg_config --pkglibdir
/opt/postgres-7.4.1//lib
Really weird.
One thing I have thought of is, shouldn't there be an etc directory in
/opt/postgres-7.4.1:
[EMAIL PROTECTED] postg
"Thomas Borg Salling" <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] postgres]$ pg_config --pkglibdir
> /opt/postgres-7.4.1//lib
Hmm. I wonder if the double slash could be causing a problem? I
wouldn't think so, but we're running out of ideas. Could you try
rebuilding with the trailing slash l
Hi again :-)
I replaced "$libdir" with "/opt/postgres-7.4.1/lib" throughout
/opt/postgres-7.4.1/share/conversion_create.sql -- then initdb succeeded!
I think this'll work for now :-). Thanks for your time and effort!
/Thomas.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PRO
"Thomas Borg Salling" <[EMAIL PROTECTED]> writes:
> I replaced "$libdir" with "/opt/postgres-7.4.1/lib" throughout
> /opt/postgres-7.4.1/share/conversion_create.sql -- then initdb succeeded!
Well, that proves the shared library wasn't broken, but it leaves us
no wiser about what the problem really
Hi,
Running postgresql v7.3 on RH7.3 linux; db creation fails
and is reproducible after a fresh image install. Any subsequent rebooting seems
to work fine.
We start up Postgres, create users and db using a Java
(IBM1.4.1) class. The following commands are executed in the following orde
Hi Tom,
I am running a Red Hat 9.0 on a Dell server.
On the datafiles I created using the "absolute path"-hack to replace
$libdir, I started postmaster. I configured postgresql.conf to accept tcp
connections. I then ran
[EMAIL PROTECTED] postgres]$ /opt/postgres-7.4.1/bin/createdb testdb
CREATE
"Thomas Borg Salling" <[EMAIL PROTECTED]> writes:
> Does this give you any clues ?
That's what I expected, but it doesn't tell me anything new. Could you
try strace-ing the backend while you execute the CREATE FUNCTION
command?
regards, tom lane
-
"Thomas Borg Salling" <[EMAIL PROTECTED]> writes:
> createdb, and started psql to create function. The result from strace (when
> running the CREATE FUNCTION) of the backend is:
> "Q\0\0\0\237CREATE OR REPLACE FUNCTION "..., 8192, 0) = 160
> gettimeofday({1075756990, 462661}, NULL) = 0
> stat64("/
Yes; you're right. Sorry. Meanwhile, I also discovered, my RedHat may
originally have put a competing postgres onto the system from some RPM.
[EMAIL PROTECTED] root]# rpm -q postgresql
postgresql-7.2.1-5
So now I've done:
[EMAIL PROTECTED] root]# rpm --erase postgresql postgresql-server
postgresq
So, I removed dfmgr.o, and remade it:
[EMAIL PROTECTED] fmgr]$ make
gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes
-Wmissing-declarations -I../../../../src/include -D_GNU_SOURCE
-DPKGLIBDIR=\"/opt/postgres-7.4.1//lib\" -DDLSUFFIX=\".so\" -c -o dfmgr.o
dfmgr.c
/usr/bin/ld -r -o SUBSYS.o d
"Thomas Borg Salling" <[EMAIL PROTECTED]> writes:
> Here is the strace (with my comments in -shes):
It looks like you strace'd the postmaster ... I wanted the backend
subprocess that's spawned for the particular psql connection.
regards, tom lane
-
Hi again,
Here is the strace (with my comments in -shes):
[EMAIL PROTECTED] postgres]$ strace /opt/postgres-7.4.1/bin/postmaster -D
/data/postgres/ -i
execve("/opt/postgres-7.4.1/bin/postmaster",
["/opt/postgres-7.4.1/bin/postmaster", "-D", "/data/postgres/", "-i"], [/*
27 vars */]) = 0
uname
18 matches
Mail list logo