Re: snprintf assert is broken by plpgsql #option dump

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: snprintf assert is broken by plpgsql #option dump
Date: 2018-10-04 21:57:53
Message-ID: 20541.1538690273@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:
> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
>> I found two parts

> Thanks for the report, will push something.

On closer look, I'm not sure that these are the only places that are
assuming that any PLpgSQL_variable struct has a refname. What seems
like a safer answer is to make sure they all do, more or less as
attached.

regards, tom lane

Attachment Content-Type Size
assign-valid-refname-for-plpgsql-rows-1.patch text/x-diff 3.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2018-10-04 21:59:37 Re: Segfault when creating partition with a primary key and sql_drop trigger exists
Previous Message Tom Lane 2018-10-04 21:17:14 Re: snprintf assert is broken by plpgsql #option dump