On 05/03/23 22:21, Tom Lane wrote:
Ankit Kumar Pandey writes:
> From my observation, we only account for data in cost computation but
> not number of columns sorted.
> Should we not account for number of columns in sort as well?
I'm not sure whether simply charging more for 2 sort column
Ankit Kumar Pandey writes:
> From my observation, we only account for data in cost computation but
> not number of columns sorted.
> Should we not account for number of columns in sort as well?
I'm not sure whether simply charging more for 2 sort columns than 1
would help much. The traditional
Hi,
This was noticed in
https://www.postgresql.org/message-id/caaphdvo2y9s2ao-bpyo7gmpyd0xe2lo-kflnqx80fcftqbc...@mail.gmail.com
I am bringing it up again.
Consider the following example:
Setup (tuple should be in memory to avoid overshadowing of disk I/O in
the experimentation):
work_me
