Re: BUG #4835: psql server crashes when using non-existing functions

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: David Sommerseth <dazo(at)users(dot)sourceforge(dot)net>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4835: psql server crashes when using non-existing functions
Date: 2009-06-03 13:37:19
Message-ID: 4A267C8F.9060603@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

David Sommerseth wrote:
> The following bug has been logged online:
>
> Bug reference: 4835
> Logged by: David Sommerseth
> Email address: dazo(at)users(dot)sourceforge(dot)net
> PostgreSQL version: 8.3.7
> Operating system: Linux (Gentoo Hardened 2008 / x86 - 32bit)
> Description: psql server crashes when using non-existing functions
> Details:
>
> (This might be a duplicate of a mail I tried to send directly to the mailing
> list, sorry if it gets dupped. I didn't find my report in the archives.
> This new entry, via the web form, got more information as well)
>
> I discovered this issue when upgrading from 8.3.5 to 8.3.7
>
> ...
>
> I degraded to 8.3.5 again, and this behaviour disappeared.
>
> The behaviour is sometimes better when the non-existing function do not
> start with 'pg_', as it seems to recover better. But not always.

Can you get a core dump, and post the gdb backtrace?

ulimit -c unlimited
pg_ctl start
< do the test to cause segfault>
gdb $PGDATA/core
bt

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2009-06-03 14:01:13 Re: BUG #4836: Losing data
Previous Message Haitham Isac 2009-06-03 12:38:25 BUG #4836: Losing data