| From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | empty column name in error message |
| Date: | 2019-12-17 06:47:07 |
| Message-ID: | CA+HiwqFA+BGyBFimjiYXXMa2Hc3fcL0+OJOyzUNjhU4NCa_XXw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
I wonder if it's worthwhile to fix the following not-so-friendly error message:
create index on foo ((row(a)));
ERROR: column "" has pseudo-type record
For example, the attached patch makes it this:
create index on foo ((row(a)));
ERROR: column "row" has pseudo-type record
Note that "row" as column name has been automatically chosen by the caller.
Thanks,
Amit
| Attachment | Content-Type | Size |
|---|---|---|
| ConstructTupleDescriptor-set-attname-earlier.patch | application/octet-stream | 1.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2019-12-17 06:50:11 | Re: Allow cluster owner to bypass authentication |
| Previous Message | Kyotaro Horiguchi | 2019-12-17 06:30:52 | Re: non-exclusive backup cleanup is mildly broken |