Re: Potential reference miscounts and segfaults in plpython.c

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jan Urbański <wulczer(at)wulczer(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Potential reference miscounts and segfaults in plpython.c
Date: 2012-02-21 17:05:57
Message-ID: 1329843957.12726.3.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On sön, 2012-02-19 at 22:29 -0500, Tom Lane wrote:
> My only comment is whether elog(ERROR) is appropriate, ie, do we
> consider these to be internal errors that users will never see in
> practice? If there's a significant risk of the error being thrown in
> the field, it might be better to use ereport, to expose the message
> for translation.

I find the wording of the error messages a bit inappropriate. For
example,

list = PyList_New(length);
+ if (list == NULL)
+ elog(ERROR, "could not transform Python list to array");

The error is not about the transforming, it's about creating a new list.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2012-02-21 17:16:35 Re: [COMMITTERS] pgsql: Correctly initialise shared recoveryLastRecPtr in recovery.
Previous Message Jeff Janes 2012-02-21 16:54:03 Re: leakproof