| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Andy Fan <zhihuifan1213(at)163(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Better error messages for %TYPE and %ROWTYPE in plpgsql |
| Date: | 2024-02-27 01:27:24 |
| Message-ID: | 2016194.1708997244@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Mon, Feb 26, 2024 at 5:46 PM Andy Fan <zhihuifan1213(at)163(dot)com> wrote:
>> Looks this modify the error message,
Well, yeah, that's sort of the point.
>> 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.
Indeed, I did not intend this for back-patch. However, I'm having
a hard time seeing the errors in question as something you'd have
automated handling for, so I don't grasp why you would think
there's a compatibility hazard.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Xing Guo | 2024-02-27 01:41:45 | Re: Control your disk usage in PG: Introduction to Disk Quota Extension |
| Previous Message | Michael Paquier | 2024-02-27 01:27:13 | Re: Sequence Access Methods, round two |