Re: [HACKERS] Increase pltcl test coverage - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Increase pltcl test coverage
Date
Msg-id 29889.1484011674@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Increase pltcl test coverage  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
Jim Nasby <Jim.Nasby@bluetreble.com> writes:
> On 1/9/17 5:38 PM, Tom Lane wrote:
>> Yeah.  I looked at that but couldn't get terribly excited about it,
>> because AFAICS, Tcl in general is apt to fall over under sufficient
>> memory pressure.

> Though, since a memory error could just as likely come out of tcl, which 
> is going to panic us anyway, I guess it doesn't matter.

Exactly.  I can't get excited about making our code slower and less
readable if there's only a fifty-fifty chance that doing so avoids a
crash.  Tcl users just need to stay far away from OOM conditions.

(If it were a more popular language, maybe there would be reason to
try to push to improve this, but ...)
        regards, tom lane



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: [HACKERS] RustgreSQL
Next
From: Jim Nasby
Date:
Subject: Re: [HACKERS] pg_background contrib module proposal