| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Erik Wienhold <ewie(at)ewie(dot)name> |
| Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Add column name to error description |
| Date: | 2025-03-07 03:57:45 |
| Message-ID: | 941921.1741319865@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Erik Wienhold <ewie(at)ewie(dot)name> writes:
> On 2025-03-07 04:05 +0100, Tom Lane wrote:
>> I think the idea of the original coding was to keep those values in
>> registers in the inner loop rather than re-fetching them each time.
> Could be. But the main reason was to hold the output column type as the
> inner loop repurposed att for the input column.
[ shrug... ] "git blame" traces this code to my commit 12b1b5d83
of 2004-12-11. I admit that my memory might be faulty 20 years later,
but that's my impression of what I was thinking.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Naylor | 2025-03-07 03:58:16 | Re: Doc fix of aggressive vacuum threshold for multixact members storage |
| Previous Message | Amit Kapila | 2025-03-07 03:51:23 | Re: Separate GUC for replication origins |