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

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: PL/Python: Fix potential NULL pointer dereference
Date: 2017-11-28 18:35:13
Message-ID: a1f87b42-fd0c-e985-ff35-79e6ad5c890e@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On 11/28/17 11:35, Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>> PL/Python: Fix potential NULL pointer dereference
>
> I do not think it's correct to just "return" out of the middle
> of a PG_TRY block --- doesn't that result in failing to pop the
> PG_exception_stack and error_context_stack?

OK, I'll revert and rethink.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2017-11-28 18:56:18 pgsql: Revert "PL/Python: Fix potential NULL pointer dereference"
Previous Message Robert Haas 2017-11-28 17:21:52 pgsql: Fix ReinitializeParallelDSM to tolerate finding no error queues.