Re: BUG #5862: Postgres dumps core upon a connection attempt

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: Matt Zinicola <matt(at)zinicola(dot)com>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5862: Postgres dumps core upon a connection attempt
Date: 2011-02-03 02:11:51
Message-ID: 4D4A0EE7.6040502@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 03/02/11 09:53, Matt Zinicola wrote:
> Apologies for lack of detail. Although I've been using Postgres for
> years, this is the first time I've had such an issue.
>
> Build options were only --with-perl and --with-python
>
> Below is the output when two different applications attempt to connect
> to my 9.0.3 server (note, the second is psql itself):
>
> [root(at)infinity postgres]# /etc/init.d/archiveopteryx start
> Starting Archiveopteryx: aox: Couldn't connect to PostgreSQL. (on
> backend 1)
> /etc/init.d/archiveopteryx: line 24: 4240 Segmentation
> fault /usr/local/archiveopteryx/bin/aox start
> done.
>
> [postgres(at)infinity scripts]$ psql template1
> Segmentation fault (core dumped)

OK, so it's not the PostgreSQL backend that's crashing, it's psql.

You almost certainly have conflicting libraries lurking around
somewhere, so psql was built against one libpq but lands up getting
linked to another at runtime.

--
System & Network Administrator
POST Newspapers

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Matt Zinicola 2011-02-03 02:33:35 Re: BUG #5862: Postgres dumps core upon a connection attempt
Previous Message Matt Zinicola 2011-02-03 01:53:11 Re: BUG #5862: Postgres dumps core upon a connection attempt