| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Vladimir Churyukin <vladimir(at)churyukin(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Improving inferred query column names |
| Date: | 2023-02-22 20:40:22 |
| Message-ID: | 20230222204022.uc4i5fm43ba67pjx@awork3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2023-02-11 12:47:04 -0800, Vladimir Churyukin wrote:
> That is a good idea for simple cases, I'm just curious how it would look
> like for more complex cases (you can have all kinds of expressions as
> parameters for aggregate function calls).
> If it works only for simple cases, I think it would be confusing and not
> very helpful.
I don't think it needs to be perfect to be helpful.
> Wouldn't it make more sense to just deduplicate the names by adding
> numerical postfixes, like sum_1, sum_2?
That'd be considerably worse than what we do today imo, because any reordering
/ added aggregate would lead to everything else changing as well.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2023-02-22 20:42:21 | Re: pg_regress: Treat child process failure as test failure |
| Previous Message | Andres Freund | 2023-02-22 20:38:48 | Re: Improving inferred query column names |