Re: backend process crash - PL/pgSQL functions - parsing problem?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: damonhart(at)yahoo(dot)com (Damon Hart)
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: backend process crash - PL/pgSQL functions - parsing problem?
Date: 2003-02-06 21:15:57
Message-ID: 15793.1044566157@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

damonhart(at)yahoo(dot)com (Damon Hart) writes:
> The postgresql log indicates that the backend is crashing with
> SIGSEGV. This is postgreSQL 7.2 running on Linux (Intel, roughly
> Mandrake 8.2)

> I adjusted whatever came to mind in the functions themselves until,
> just by luck, I found that if I shortened the length of the function
> names, the crash disappeared.

I think this is probably due to this bug:

2002-05-05 13:38 tgl

* src/pl/plpgsql/src/pl_funcs.c (REL7_2_STABLE):
plpgsql_dstring_append was broken for long strings.

If so, updating to 7.2.2 or later should fix it.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Greg Stark 2003-02-06 21:17:15 optimizer not eliminating redundant sorts
Previous Message Tom Lane 2003-02-06 21:13:08 Re: Cannot insert a duplicate key into unique index pg_calss_oid_index