Re: Better error messages for %TYPE and %ROWTYPE in plpgsql

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Andy Fan <zhihuifan1213(at)163(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Better error messages for %TYPE and %ROWTYPE in plpgsql
Date: 2024-02-27 00:54:05
Message-ID: CAKFQuwZcjuP6voxs9Qn4y7Lf3qSonVE-aBVes9HqVZ7FmvPY5g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Feb 26, 2024 at 5:46 PM Andy Fan <zhihuifan1213(at)163(dot)com> wrote:

> > Per recent discussion[1], plpgsql returns fairly unhelpful "syntax
> > error" messages when a %TYPE or %ROWTYPE construct references a
> > nonexistent object. Here's a quick little finger exercise to try
> > to improve that.
>
> Looks this modify the error message, I want to know how ould we treat
> error-message-compatible issue during minor / major upgrade.
>

There is no bug here so no back-patch; and we are not yet past feature
freeze for v17.

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2024-02-27 01:27:13 Re: Sequence Access Methods, round two
Previous Message Andy Fan 2024-02-27 00:40:17 Re: Better error messages for %TYPE and %ROWTYPE in plpgsql