Re: pgsql: PL/Python: Fix potential NULL pointer dereference

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: PL/Python: Fix potential NULL pointer dereference
Date: 2017-12-12 21:42:59
Message-ID: 25438.1513114979@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> On 12/5/17 14:45, Tom Lane wrote:
>> On the whole it seems like it might be better to dodge this whole business
>> of changing "result" inside the TRY. You could do that if you did
>> something like ...

> Yeah, that looks much better. Next try attached.

Looks sane to me.

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2017-12-13 00:37:27 pgsql: Remove obsolete comment.
Previous Message Peter Eisentraut 2017-12-12 17:10:21 Re: pgsql: PL/Python: Fix potential NULL pointer dereference