Re: Postgres Crash Running PLPGSQL Function on 8.2.3

I need to extract the necessary database components to repro the problem
and find out how much data it will require. I will need some time to
prepare that for sending. I should be able to prepare something today,
or tomorrow.

My Thanks for giving this problem attention. Until this is fixed, I
can't upgrade past this point (v8.1.8).

As said previously, my code works perfectly on 8.1.8 on Windows 2003
SP1. A colleague of mine tested my code on a Postgres 8.2.3 running on
FreeBSD, and it too ran without incident.

-----Original Message-----
From: pgsql-general-owner(at)postgresql(dot)org
[mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of Tom Lane
Sent: Monday, April 09, 2007 4:48 PM
To: Gary Winslow
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] Postgres Crash Running PLPGSQL Function on 8.2.3

"Gary Winslow" <gary(dot)winslow(at)atfs(dot)com> writes:
> I would be happy to provide a "self-contained" test case. I would
have
> to send to you a pg_dump of it which would be rather large to send via
> email. Some of the code includes confidential business specific calc
> rules that I cannot release to the general public.

Understood; it won't go anywhere. But how large is "rather large"?
Can you duplicate the problem with no (or less) data?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match