From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Richard Guo <guofenglinux(at)gmail(dot)com>, Alexandra Wang <alexandra(dot)wang(dot)oss(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "bruce(at)momjian(dot)us" <bruce(at)momjian(dot)us>, lepihov(at)gmail(dot)com |
Subject: | Re: plan shape work |
Date: | 2025-09-15 21:15:44 |
Message-ID: | 666191.1757970944@sss.pgh.pa.us |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Well, I was just bringing it up because you seemed to think that the
> Replaces: line was not necessarily where we would have put it in a
> green field. I am not sure about where we would have put it, but I
> think in a green field we wouldn't have it at all, and I actually
> think the above is worth considering. I think people would get used to
> it pretty fast and that it might be more clear than "Result", which
> doesn't really mean a whole lot. However, if you or others don't like
> that and you want to just move the Replaces line slightly higher in
> the output, I mean, I don't mind that, I just don't know that it's
> really a material difference.
Yeah, I'm content with making it a "Replaces" attribute, I'm just
complaining about the ordering. I'd be the first to agree that
this is purely cosmetic, but in my mind there is a pretty clear
precedence ordering among the attributes that EXPLAIN prints.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Sami Imseih | 2025-09-15 21:47:27 | Re: PgStat_HashKey padding issue when passed by reference |
Previous Message | Tom Lane | 2025-09-15 21:12:38 | Re: Identifying function-lookup failures due to argument name mismatches |