On Wed, 24 Jan 2007, Tom Lane wrote:
Somehow DBD::Pg picked up the wrong (older) version of libpq.so; you need
to look into why. Wrong search path while building maybe?
Tom,
I _thought_ that might be what happened, but I wanted to make sure before
I dug myself into a hole.
You are absol
Rich Shepard <[EMAIL PROTECTED]> writes:
>I'm not following you. DBD::Pg is the most current version (1.49 from May
> 2006). That I built and installed this morning. It's calling
> /usr/lib/libpg.so.3.1, but I also have /usr/lib/ligpg.so.4.1.
Somehow DBD::Pg picked up the wrong (older) version
On Wed, 24 Jan 2007, Alan Hodgson wrote:
It'll be whatever version the DBD::Pg module is compiled to use. Just
rebuilding and installing an updated version of that package will likely
fix your problem.
Alan,
I'm not following you. DBD::Pg is the most current version (1.49 from May
2006). T
On 1/24/07, Rich Shepard <[EMAIL PROTECTED]> wrote:
libpq.so.3 => /usr/lib/libpq.so.3 (0xb7f5f000)
So it's finding all the libraries it wants, and it's using the older
libpq.so. Interesting.
Where is your other installation of PostgreSQL installed? I suspect this is
because somewhe
On Wed, 24 Jan 2007, Martijn van Oosterhout wrote:
Method 1: Find the .so module that perl uses (try locate Pg.so and ldd
that).
Martijn,
Thank you for teaching me a new trick today. The results of method 1 are:
/lib/libsafe.so.2 (0xb7f76000)
linux-gate.so.1 => (0xe000
On Wed, Jan 24, 2007 at 01:08:04PM -0800, Rich Shepard wrote:
> >The server doesn't care, what matter is what version the *client* (in this
> >case SQL-Ledger) expects. ldd should tell you that.
>
> Martijn,
>
> OK. I'll go back there (which is where I started this journey). I don't
> know how
On Wednesday 24 January 2007 13:08, Rich Shepard
<[EMAIL PROTECTED]> wrote:
>OK. I'll go back there (which is where I started this journey). I
> don't know how to run ldd on a perl script.
It'll be whatever version the DBD::Pg module is compiled to use. Just
rebuilding and installing an upd
On Wed, 24 Jan 2007, Martijn van Oosterhout wrote:
What version of libpq.so do I need?
The server doesn't care, what matter is what version the *client* (in this
case SQL-Ledger) expects. ldd should tell you that.
Martijn,
OK. I'll go back there (which is where I started this journey).
On Wed, Jan 24, 2007 at 12:02:30PM -0800, Rich Shepard wrote:
> I got postmaster running now, but have been blocked by Bug #2701 when I
> try to run SQL-Ledger. Google has 1,830 hits for it, so I'm far from the
> first. :-)
>
> I'm running -8.1.4 here. In /usr/lib/ I have:
> What version
On Wed, 24 Jan 2007, Tom Lane wrote:
Have you looked in the postmaster log?
Tom, et al.:
I got postmaster running now, but have been blocked by Bug #2701 when I
try to run SQL-Ledger. Google has 1,830 hits for it, so I'm far from the
first. :-)
I'm running -8.1.4 here. In /usr/lib/ I hav
On Wed, 24 Jan 2007, Tom Lane wrote:
Have you looked in the postmaster log?
Tom,
I went looking for it before writing, but did not find it. Now I have.
The ownership and permissions of /var/lib/pgsql and /var/lib/postgresql were
FUBAR.
I changed the permissions and it's now running.
Tha
Rich Shepard <[EMAIL PROTECTED]> writes:
> When I run '/etc/rc.d/rc.postgresql start' it returns 'Starting
> PostgreSQL: ok', but '/etc/rc.d/rc.postgresql status' returns 'pg_ctl:
> neither postmaster nor postgres running' which is true.
Have you looked in the postmaster log? Under almost all
I had a problem with SQL-Ledger running on the local httpd that traced
back to some crufty old libpg.so* from 2003 and 2004 in /usr/local/lib. I
removed those (saved them, actually), ran ldconfig, then restarted both
httpd and postgresql. Unfortunately, the latter really has not started
despite
13 matches
Mail list logo
