Re: Improving contrib/tablefunc's error reporting

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Improving contrib/tablefunc's error reporting
Date: 2024-03-09 18:07:17
Message-ID: 1069256.1710007637@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joe Conway <mail(at)joeconway(dot)com> writes:
> On 3/5/24 17:04, Tom Lane wrote:
>> After reading the thread at [1], I could not escape the feeling
>> that contrib/tablefunc's error reporting is very confusing.

> The changes all look good to me and indeed more consistent with the docs.
> Do you want me to push these? If so, development tip only, or backpatch?

I can push that. I was just thinking HEAD, we aren't big on changing
error reporting in back branches.

>> BTW, while I didn't touch it here, it seems fairly bogus that
>> connectby() checks both type OID and typmod for its output
>> columns while crosstab() only checks type OID. I think
>> crosstab() is in the wrong and needs to be checking typmod.
>> That might be fit material for a separate patch though.

> I can take a look at this. Presumably this would not be for backpatching.

I'm not sure whether that could produce results bad enough to be
called a bug or not. But I too would lean towards not back-patching,
in view of the lack of field complaints.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2024-03-09 19:58:09 Re: Improving contrib/tablefunc's error reporting
Previous Message Joe Conway 2024-03-09 17:56:19 Re: Improving contrib/tablefunc's error reporting